docs: i18n: Add complete French translation#2073
Merged
alexeyv merged 5 commits intobmad-code-org:mainfrom Mar 20, 2026
Merged
Conversation
📝 WalkthroughWalkthroughComprehensive French documentation suite added for the BMad development methodology, including 31 markdown files covering getting-started tutorials, how-to guides, conceptual explanations, references, installation/upgrade instructions, and a roadmap. All files follow consistent structure with front-matter metadata and adhere to a defined style guide. Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~15 minutes Possibly related PRs
Suggested reviewers
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
📝 Coding Plan
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 Tip CodeRabbit can generate a title for your PR based on the changes.Add |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 7
🧹 Nitpick comments (1)
docs/fr/reference/core-tools.md (1)
288-288: Minor wording polish for imperative consistency.Consider
Regroupe les fichiers...instead ofGroupe les fichiers...to keep the procedural imperative style consistent with adjacent steps.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@docs/fr/reference/core-tools.md` at line 288, Change the imperative wording "Groupe les fichiers par type, objectif ou sous-répertoire" to "Regroupe les fichiers par type, objectif ou sous-répertoire" so the step uses the consistent procedural form used in adjacent steps; locate the exact sentence in docs/fr/reference/core-tools.md and replace the initial verb token "Groupe" with "Regroupe".
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@docs/fr/explanation/established-projects-faq.md`:
- Line 46: Fix the grammar in the decision branch string by changing "dans le
spécification technique" to the correct feminine form "dans la spécification
technique" wherever the phrase appears (specifically replace the text "- **Non**
→ Établir de nouvelles normes (documenter pourquoi dans le spécification
technique)" so it reads "- **Non** → Établir de nouvelles normes (documenter
pourquoi dans la spécification technique)").
In `@docs/fr/how-to/customize-bmad.md`:
- Around line 58-62: Several YAML examples use single-quoted strings that either
contain typographic quotes or escaped apostrophes and therefore fail parsing;
update the YAML snippets (e.g., the agent.metadata.name example and other
agent/metadata string examples) to use double-quoted strings instead so
apostrophes don’t need escaping and typographic quotes are preserved, replacing
occurrences of typographic right single quote and backslash-escaped apostrophes
(\' ) with standard double-quoted values (e.g., "Bob l’éponge") in the examples
and ensure all single-quoted usages that include apostrophes are converted
consistently.
In `@docs/fr/how-to/project-context.md`:
- Line 28: Fix the plural agreement typo in the Option C description: replace
the phrase "les base de code existantes" with the correct plural form "les bases
de code existantes" in the line that starts with "Génération pour les projets
existants" (Option C).
In `@docs/fr/reference/agents.md`:
- Line 14: The documented skill IDs omit the `-agent-` segment and must match
the installed skill manifests; update the strings `bmad-analyst`,
`bmad-architect`, `bmad-ux-designer`, and `bmad-tech-writer` to the correct IDs
`bmad-agent-analyst`, `bmad-agent-architect`, `bmad-agent-ux-designer`, and
`bmad-agent-tech-writer` (also propagate the same correction for the other
occurrences noted on lines 20–23) so that invocations reference the exact skill
manifest IDs.
In `@docs/fr/reference/commands.md`:
- Around line 23-24: La phrase actuelle implique que tous les skills sont
limités aux « modules sélectionnés » — corrigez-la pour préciser que lors de
l'exécution de `npx bmad-method install` l'installateur lit les manifests et
crée un skill par agent, workflow, tâche et outil, mais que seuls les agents
sont scoped par module tandis que les workflows et les tasks sont des artefacts
cross-cutting installés globalement (conserver la mention des SKILL.md).
Ré-écrivez la ligne pour distinguer explicitement "agents (module-scoped)" vs
"workflows/tâches (installés globalement)" afin d'éviter l'ambiguïté.
In `@docs/fr/reference/modules.md`:
- Around line 74-76: Mettre à jour le paragraphe sous le titre "Modules
Communautaires" pour supprimer l'affirmation "à venir" et indiquer que des
modules communautaires existent déjà; remplacer la phrase actuelle par une
formulation indiquant que des modules communautaires sont disponibles et pointer
vers l'organisation GitHub BMad pour les mises à jour, en mentionnant
explicitement le module existant "whiteport-design-studio" (ou ajouter un lien
vers son dépôt) afin d'éviter toute confusion.
In `@docs/fr/roadmap.mdx`:
- Line 88: The roadmap line that currently reads "Conversations sur le
développement natif IA. Lancement le 1er mars 2026 !" is stale; change the
phrasing to reflect that the launch has already occurred (e.g., "Conversations
sur le développement natif IA. Lancé le 1er mars 2026 !" or "… Lancement
effectué le 1er mars 2026.") so the status is no longer described as
upcoming—update the sentence containing that exact text accordingly.
---
Nitpick comments:
In `@docs/fr/reference/core-tools.md`:
- Line 288: Change the imperative wording "Groupe les fichiers par type,
objectif ou sous-répertoire" to "Regroupe les fichiers par type, objectif ou
sous-répertoire" so the step uses the consistent procedural form used in
adjacent steps; locate the exact sentence in docs/fr/reference/core-tools.md and
replace the initial verb token "Groupe" with "Regroupe".
🪄 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: bb4dde76-2b03-4287-88a2-d29005bd75b8
⛔ Files ignored due to path filters (4)
website/astro.config.mjsis excluded by!website/**website/public/diagrams/quick-dev-diagram-fr.webpis excluded by!website/**website/public/workflow-map-diagram-fr.htmlis excluded by!website/**website/src/content/i18n/fr-FR.jsonis excluded by!website/**
📒 Files selected for processing (29)
docs/fr/404.mddocs/fr/_STYLE_GUIDE.mddocs/fr/explanation/advanced-elicitation.mddocs/fr/explanation/adversarial-review.mddocs/fr/explanation/brainstorming.mddocs/fr/explanation/established-projects-faq.mddocs/fr/explanation/party-mode.mddocs/fr/explanation/preventing-agent-conflicts.mddocs/fr/explanation/project-context.mddocs/fr/explanation/quick-dev.mddocs/fr/explanation/why-solutioning-matters.mddocs/fr/how-to/customize-bmad.mddocs/fr/how-to/established-projects.mddocs/fr/how-to/get-answers-about-bmad.mddocs/fr/how-to/install-bmad.mddocs/fr/how-to/non-interactive-installation.mddocs/fr/how-to/project-context.mddocs/fr/how-to/quick-fixes.mddocs/fr/how-to/shard-large-documents.mddocs/fr/how-to/upgrade-to-v6.mddocs/fr/index.mddocs/fr/reference/agents.mddocs/fr/reference/commands.mddocs/fr/reference/core-tools.mddocs/fr/reference/modules.mddocs/fr/reference/testing.mddocs/fr/reference/workflow-map.mddocs/fr/roadmap.mdxdocs/fr/tutorials/getting-started.md
Comment on lines
+74
to
+76
| ## Modules Communautaires | ||
|
|
||
| Les modules communautaires et une marketplace de modules sont à venir. Consultez l'[organisation GitHub BMad](https://github.com/bmad-code-org) pour les mises à jour. |
There was a problem hiding this comment.
Corriger l’affirmation sur les modules communautaires (déjà disponibles).
La phrase de Line 76 indique que les modules communautaires sont “à venir”, alors qu’au moins un module communautaire est déjà défini (whiteport-design-studio). Cela peut induire les utilisateurs en erreur.
Proposition de correction
## Modules Communautaires
-Les modules communautaires et une marketplace de modules sont à venir. Consultez l'[organisation GitHub BMad](https://github.com/bmad-code-org) pour les mises à jour.
+Des modules communautaires existent déjà, et une marketplace de modules est à venir. Consultez l'[organisation GitHub BMad](https://github.com/bmad-code-org) pour les mises à jour.📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
Suggested change
| ## Modules Communautaires | |
| Les modules communautaires et une marketplace de modules sont à venir. Consultez l'[organisation GitHub BMad](https://github.com/bmad-code-org) pour les mises à jour. | |
| ## Modules Communautaires | |
| Des modules communautaires existent déjà, et une marketplace de modules est à venir. Consultez l'[organisation GitHub BMad](https://github.com/bmad-code-org) pour les mises à jour. |
🧰 Tools
🪛 LanguageTool
[grammar] ~74-~74: « communautaires » semble plus probable dans ce contexte
Context: ...tégrations MCP optionnelles ## Modules Communautaires Les modules communautaires et une market...
(QB_NEW_FR_OTHER_ERROR_IDS_REPLACEMENT_ORTHOGRAPHY_UPPERCASE)
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@docs/fr/reference/modules.md` around lines 74 - 76, Mettre à jour le
paragraphe sous le titre "Modules Communautaires" pour supprimer l'affirmation
"à venir" et indiquer que des modules communautaires existent déjà; remplacer la
phrase actuelle par une formulation indiquant que des modules communautaires
sont disponibles et pointer vers l'organisation GitHub BMad pour les mises à
jour, en mentionnant explicitement le module existant "whiteport-design-studio"
(ou ajouter un lien vers son dépôt) afin d'éviter toute confusion.
| <div class="roadmap-future-card"> | ||
| <span class="roadmap-emoji">🎙️</span> | ||
| <h4>Le Podcast de la Méthode BMad</h4> | ||
| <p>Conversations sur le développement natif IA. Lancement le 1er mars 2026 !</p> |
There was a problem hiding this comment.
Past-dated launch statement is now stale.
Line 88 says “Lancement le 1er mars 2026 !”, but that date is already past (March 1, 2026). Please update wording to reflect actual status (launched vs upcoming) to avoid roadmap confusion.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@docs/fr/roadmap.mdx` at line 88, The roadmap line that currently reads
"Conversations sur le développement natif IA. Lancement le 1er mars 2026 !" is
stale; change the phrasing to reflect that the launch has already occurred
(e.g., "Conversations sur le développement natif IA. Lancé le 1er mars 2026 !"
or "… Lancement effectué le 1er mars 2026.") so the status is no longer
described as upcoming—update the sentence containing that exact text
accordingly.
Add comprehensive French (fr-FR) translation covering all documentation sections and website configuration: - Core docs, How-to guides, Explanations, References - Website config: astro.config.mjs locale setup, fr-FR.json i18n strings - Assets: French workflow map diagram and quick-dev diagram Terminology standardized on "Quick Dev" (replacing legacy "Quick Flow").
Remove all references to deleted phase-4 agent personas from French documentation, matching upcoming PR bmad-code-org#2020 changes: - Remove agent personas: dev/Amelia, pm/John, qa/Quinn, sm/Bob, quick-flow-solo-dev/Barry, bmad-master - Replace deleted agent skill invocations with equivalent workflow skills (bmad-dev-story, bmad-qa-generate-e2e-tests, bmad-quick-dev, etc.) - Depersonalize QA references ("Quinn" → "QA Intégré" / "Workflow QA") - Simplify workflow invocation instructions (remove "invoke agent" pattern) - Fix upgrade-to-v6.md SM/Scrum Master references
Collaborator
|
Thank you for this PR. There are two big questions we need to discuss before we can take this in:
This is best discussed on Discord, so can you please PM BMadCode or myself over there about this? |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This PR adds a complete French (fr-FR) translation of the BMad Method documentation, making the framework accessible to French-speaking people.
Changes
Documentation
docs/fr/Core docs, How-to guides, Explanations, References
I kept
/frroute instead of full/fr-frsince it's not common to have multiple french variations.Website Configuration
astro.config.mjs: French locale configuration with sidebar translationswebsite/src/content/i18n/fr-FR.json: Starlight UI strings in FrenchAssets
workflow-map-diagram-fr.html: French version of the workflow mapquick-dev-diagram-fr.webp: French Quick Dev diagramTerminology
Standardized on "Quick Dev" throughout (replacing legacy "Quick Flow" terminology).
Upcoming changes reflected in this translation