docs(ko-kr): add Korean localization#2386
Conversation
📝 WalkthroughWalkthroughThis 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. ChangesKorean Documentation Translation
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Possibly related PRs
Suggested reviewers
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
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
docs/ko-kr/roadmap.mdxOops! 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. https://eslint.org/docs/latest/use/configure/migration-guide If you still have problems after following the migration guide, please stop by 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.
Built for teams:
One agent for your entire SDLC. Right inside Slack. 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. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
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
⛔ Files ignored due to path filters (4)
website/astro.config.mjsis excluded by!website/**website/src/components/Banner.astrois excluded by!website/**website/src/content/i18n/ko-KR.jsonis excluded by!website/**website/src/lib/locales.mjsis excluded by!website/**
📒 Files selected for processing (36)
README_KR.mddocs/ko-kr/404.mddocs/ko-kr/_STYLE_GUIDE.mddocs/ko-kr/explanation/advanced-elicitation.mddocs/ko-kr/explanation/adversarial-review.mddocs/ko-kr/explanation/analysis-phase.mddocs/ko-kr/explanation/brainstorming.mddocs/ko-kr/explanation/checkpoint-preview.mddocs/ko-kr/explanation/established-projects-faq.mddocs/ko-kr/explanation/forensic-investigation.mddocs/ko-kr/explanation/named-agents.mddocs/ko-kr/explanation/party-mode.mddocs/ko-kr/explanation/preventing-agent-conflicts.mddocs/ko-kr/explanation/project-context.mddocs/ko-kr/explanation/quick-dev.mddocs/ko-kr/explanation/why-solutioning-matters.mddocs/ko-kr/how-to/customize-bmad.mddocs/ko-kr/how-to/established-projects.mddocs/ko-kr/how-to/expand-bmad-for-your-org.mddocs/ko-kr/how-to/get-answers-about-bmad.mddocs/ko-kr/how-to/install-bmad.mddocs/ko-kr/how-to/install-custom-modules.mddocs/ko-kr/how-to/non-interactive-installation.mddocs/ko-kr/how-to/project-context.mddocs/ko-kr/how-to/quick-fixes.mddocs/ko-kr/how-to/shard-large-documents.mddocs/ko-kr/how-to/upgrade-to-v6.mddocs/ko-kr/index.mddocs/ko-kr/reference/agents.mddocs/ko-kr/reference/commands.mddocs/ko-kr/reference/core-tools.mddocs/ko-kr/reference/modules.mddocs/ko-kr/reference/testing.mddocs/ko-kr/reference/workflow-map.mddocs/ko-kr/roadmap.mdxdocs/ko-kr/tutorials/getting-started.md
|
Hi @yeomin4242! French translator here, Thanks for your participation for translation contribution! I think the team is more active on the weekend for merging pull requests. Few things that came to me reviewing your commits:
With this on-going effort, we may eventually get this be consistent across all doc languages, for now we have to adjust a bit manually. I’ve corrected the numbering in my current PR if you want to look at it. |
|
Thanks for pointing this out! I also updated the Korean workflow map for this PR by adding I agree that duplicating the whole HTML file is probably not the best long-term solution. Separating the text from the markup/styles would be better. For now, I followed the current localized-file approach so the Korean docs can have the translated diagram as well. I’ll also fix the Korean docs issues such as the sidebar order conflicts. Thanks! |
|
@yeomin4242 @eatse21 thanks for the contribution and comments. before merging - @yeomin4242 will you be available to every once in a while make updates as other changes come? Theres are some significant changes coming soon that will result in some major doc updates |
Thanks for the heads-up. Yes, I’d be happy to help keep the updated as the docs change. Feel free to tag me on relevant issues or PRs, and I’ll do my best to review and update them. |
|
@yeomin4242 a simple trick I use to keep track changes, is tracking the
So then you can have a quick glance on only the relevant commits of the repo, and see if some english source doc changed |
…te iframe references
alexeyv
force-pushed
the
docs/ko-kr-translation
branch
from
2e930e6 to
3e20859
Compare
|
From the recent Korean localization sync commits (
|
3 participants
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
docs/ko-krandREADME_KR.md.Testing
Ran:
npm cinpm run qualityBoth passed.
Notes:
npm cireported existing audit findings: 4 vulnerabilities, 3 moderate and 1 high.validate:skillsreported medium/low findings only; strict mode passed.