Skip to content

docs(ko-kr): add Korean localization#2386

Open
yeomin4242 wants to merge 4 commits into
bmad-code-org:mainfrom
yeomin4242:docs/ko-kr-translation
Open

docs(ko-kr): add Korean localization#2386
yeomin4242 wants to merge 4 commits into
bmad-code-org:mainfrom
yeomin4242:docs/ko-kr-translation

Conversation

@yeomin4242
Copy link
Copy Markdown

What

Add Korean localization for the BMAD Method documentation and website UI.

This adds the full Korean docs tree under docs/ko-kr, a Korean README, Korean locale registration, and localized navigation, banner, and Starlight UI strings.

Why

The repository already supports localized documentation for multiple languages, and this change adds Korean coverage for the BMAD docs set.

The translation was reviewed against the English documentation as the source of truth to improve accuracy, readability, terminology consistency, and maintainability for future updates.

How

  • Added Korean docs under docs/ko-kr and README_KR.md.
  • Added Korean locale/i18n support in website config and Starlight strings.
  • Localized Korean navigation and moved shared banner text into locale-specific copy.
  • Reworked awkward transliterations into more natural technical Korean.

Testing

Ran:

  • npm ci
  • npm run quality

Both passed.

Notes:

  • npm ci reported existing audit findings: 4 vulnerabilities, 3 moderate and 1 high.
  • validate:skills reported medium/low findings only; strict mode passed.

@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented May 16, 2026

Review Change Stack

📝 Walkthrough

Walkthrough

This pull request adds comprehensive Korean-language documentation for the BMad Method project, providing a complete translation of the English documentation structure across 54 files including project README, style guide, conceptual explanations, how-to guides, reference materials, tutorial, and public roadmap.

Changes

Korean Documentation Translation

Layer / File(s) Summary
Landing pages and site structure
README_KR.md, docs/ko-kr/index.md, docs/ko-kr/404.md
Korean project README with badges and overview, home page with feature highlights and navigation, and error page template.
Documentation style guide
docs/ko-kr/_STYLE_GUIDE.md
Comprehensive Korean writing rules, standard document templates (tutorials, guides, explanations, references, glossaries, FAQs), checklists per document type, and validation commands for link fixing and doc builds.
Conceptual explanation pages
docs/ko-kr/explanation/* (11 pages)
Korean explanations of BMad Method concepts: advanced elicitation, adversarial review, analysis phase, brainstorming, checkpoint preview workflow, established projects FAQ, forensic investigation, named agents, party mode, preventing agent conflicts, project context, quick development workflow, and why solutioning matters.
Practical how-to guides
docs/ko-kr/how-to/* (13 pages)
Korean step-by-step guides covering BMad installation and updates, customization and organizational expansion, project setup for established codebases, custom module installation, project context creation, quick fixes, document sharding, v6 migration, and finding help.
Reference documentation
docs/ko-kr/reference/* (5 pages)
Korean reference pages documenting named agents and their triggers, commands/skills, core tools with usage details, official modules, testing options (built-in QA and TEA module), and complete workflow map with stage breakdowns.
Getting-started tutorial and roadmap
docs/ko-kr/tutorials/getting-started.md, docs/ko-kr/roadmap.mdx
Korean first-time user tutorial guiding installation through first project completion, and public roadmap documenting in-progress, planned, and community-driven initiatives.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

  • bmad-code-org/BMAD-METHOD#2183: Adds English documentation for checkpoint-preview workflow that is also localized in this Korean PR.
  • bmad-code-org/BMAD-METHOD#2355: Adds Korean and Chinese localization for named-agents.md and expand-bmad-for-your-org.md, overlapping content translations.
  • bmad-code-org/BMAD-METHOD#2094: Updates installation documentation including non-interactive/CI installation details that are reflected in this Korean localization.

Suggested reviewers

  • alexeyv
  • bmadcode
🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly summarizes the main change: adding Korean localization to documentation and website UI, which matches the changeset content.
Description check ✅ Passed The description is directly related to the changeset, explaining what was added (Korean docs, README, locale support), why it matters, and how it was implemented.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Warning

There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure.

🔧 ESLint

If the error stems from missing dependencies, add them to the package.json file. For unrecoverable errors (e.g., due to private dependencies), disable the tool in the CodeRabbit configuration.

docs/ko-kr/roadmap.mdx

Oops! Something went wrong! :(

ESLint: 9.39.4

ESLint couldn't find an eslint.config.(js|mjs|cjs) file.

From ESLint v9.0.0, the default configuration file is now eslint.config.js.
If you are using a .eslintrc.* file, please follow the migration guide
to update your configuration file to the new format:

https://eslint.org/docs/latest/use/configure/migration-guide

If you still have problems after following the migration guide, please stop by
https://eslint.org/chat/help to chat with the team.

Tip

💬 Introducing Slack Agent: The best way for teams to turn conversations into code.

Slack Agent is built on CodeRabbit's deep understanding of your code, so your team can collaborate across the entire SDLC without losing context.

  • Generate code and open pull requests
  • Plan features and break down work
  • Investigate incidents and troubleshoot customer tickets together
  • Automate recurring tasks and respond to alerts with triggers
  • Summarize progress and report instantly

Built for teams:

  • Shared memory across your entire org—no repeating context
  • Per-thread sandboxes to safely plan and execute work
  • Governance built-in—scoped access, auditability, and budget controls

One agent for your entire SDLC. Right inside Slack.

👉 Get started


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link
Copy Markdown

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 3

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@docs/ko-kr/reference/agents.md`:
- Line 14: The example developer skill ID in docs/ko-kr/reference/agents.md
currently uses `bmad-dev`, which conflicts with other PR docs that reference
`bmad-agent-dev`; update the example in that file to use the consistent real
skill ID `bmad-agent-dev` so users won't be given an incorrect ID (search for
the string `bmad-dev` in the file and replace it with `bmad-agent-dev`).

In `@docs/ko-kr/roadmap.mdx`:
- Line 88: Update the outdated sentence "AI 네이티브 개발에 관한 대화입니다. 2026년 3월 1일 공개
예정입니다." in the roadmap content: either remove the future-date phrase and state
it as already published (e.g., "공개됨" / "2026년 3월 1일 공개") or replace with a
date-agnostic phrase like "곧 공개 예정" or "공개 예정" as appropriate; ensure the
updated sentence preserves the original intent about the AI 네이티브 개발 대화 and
adjust surrounding wording for tense consistency.

In `@docs/ko-kr/tutorials/getting-started.md`:
- Around line 119-120: The tutorial uses inconsistent agent skill IDs (e.g.,
bmad-agent-pm, bmad-agent-architect, bmad-agent-analyst, bmad-agent-ux-designer)
that don't match the reference IDs (bmad-pm, bmad-architect, bmad-analyst,
bmad-ux-designer); update every occurrence in the getting-started.md text
(including the shown block and the other noted lines around 163, 170-171,
180-181, 186-187, 259) to use the canonical IDs (bmad-pm, bmad-architect,
bmad-analyst, bmad-ux-designer) so commands/examples will run correctly and
consistently with the reference doc.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 86abd0e9-1abb-4c09-af2d-afd2c739723a

📥 Commits

Reviewing files that changed from the base of the PR and between 5090cfb and 514f15e.

⛔ Files ignored due to path filters (4)
  • website/astro.config.mjs is excluded by !website/**
  • website/src/components/Banner.astro is excluded by !website/**
  • website/src/content/i18n/ko-KR.json is excluded by !website/**
  • website/src/lib/locales.mjs is excluded by !website/**
📒 Files selected for processing (36)
  • README_KR.md
  • docs/ko-kr/404.md
  • docs/ko-kr/_STYLE_GUIDE.md
  • docs/ko-kr/explanation/advanced-elicitation.md
  • docs/ko-kr/explanation/adversarial-review.md
  • docs/ko-kr/explanation/analysis-phase.md
  • docs/ko-kr/explanation/brainstorming.md
  • docs/ko-kr/explanation/checkpoint-preview.md
  • docs/ko-kr/explanation/established-projects-faq.md
  • docs/ko-kr/explanation/forensic-investigation.md
  • docs/ko-kr/explanation/named-agents.md
  • docs/ko-kr/explanation/party-mode.md
  • docs/ko-kr/explanation/preventing-agent-conflicts.md
  • docs/ko-kr/explanation/project-context.md
  • docs/ko-kr/explanation/quick-dev.md
  • docs/ko-kr/explanation/why-solutioning-matters.md
  • docs/ko-kr/how-to/customize-bmad.md
  • docs/ko-kr/how-to/established-projects.md
  • docs/ko-kr/how-to/expand-bmad-for-your-org.md
  • docs/ko-kr/how-to/get-answers-about-bmad.md
  • docs/ko-kr/how-to/install-bmad.md
  • docs/ko-kr/how-to/install-custom-modules.md
  • docs/ko-kr/how-to/non-interactive-installation.md
  • docs/ko-kr/how-to/project-context.md
  • docs/ko-kr/how-to/quick-fixes.md
  • docs/ko-kr/how-to/shard-large-documents.md
  • docs/ko-kr/how-to/upgrade-to-v6.md
  • docs/ko-kr/index.md
  • docs/ko-kr/reference/agents.md
  • docs/ko-kr/reference/commands.md
  • docs/ko-kr/reference/core-tools.md
  • docs/ko-kr/reference/modules.md
  • docs/ko-kr/reference/testing.md
  • docs/ko-kr/reference/workflow-map.md
  • docs/ko-kr/roadmap.mdx
  • docs/ko-kr/tutorials/getting-started.md

Comment thread docs/ko-kr/reference/agents.md
Comment thread docs/ko-kr/roadmap.mdx
Comment thread docs/ko-kr/tutorials/getting-started.md
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant