i18n(fr): update beta29 docs

[ArmandPhilippot]

Description

Updates the French translations with changes from #172

Summary by CodeRabbit

• Documentation
  • Updated French-language upgrade guide documentation with refinements to existing guides
  • Added new comprehensive upgrade guide for version 0-1-0-beta-29 with details on bug fixes and dependency updates

[coderabbitai]

📝 Walkthrough

Walkthrough

The PR removes the badge metadata from the French upgrade guide for version 0-1-0-beta-28 and introduces a new French upgrade guide for version 0-1-0-beta-29 that documents bug fixes and dependency updates including @studiocms/ui v1.0.0-beta.4.

Changes

Cohort / File(s)	Summary
French upgrade guides src/content/docs/fr/guides/upgrade/version-guides/0-1-0-beta-28.mdx	Removed badge metadata ("NOUVEAU" with success variant) from front matter
French upgrade guides src/content/docs/fr/guides/upgrade/version-guides/0-1-0-beta-29.mdx	New file: Added French upgrade guide with front matter (i18nReady, title, description, badge), component imports (ReadMore, QuickUpdate), and documentation of bug fixes and dependency updates

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

• Verify front matter metadata structure, particularly the badge format in the new file
• Confirm imported components (QuickUpdate, ReadMore) exist and are correctly referenced
• Review accuracy of documented dependency versions and changes
• Ensure i18n configuration (i18nReady) is correctly set

Possibly related PRs

• i18n(fr): update docs for beta.28 #171: Modifies the same file's (0-1-0-beta-28.mdx) frontmatter badge metadata, suggesting concurrent badge updates across French upgrade guides.
• i18n(fr): update UI strings #119: Adds French translations for "quick-update" UI strings and sidebar keys that are used by the QuickUpdate component in the new upgrade guide content.
• feat: add upgrade guide for StudioCMS Beta.29 #172: Updates upgrade guides across multiple locales for beta.28 and beta.29 versions, suggesting parallel locale-specific documentation changes.

Suggested labels

i18n

Suggested reviewers

• louisescher
• dreyfus92

Poem

🐰 A badge bade farewell to beta's past,
While new guides bloom with versions vast,
French docs now dance with QuickUpdate's grace,
Dependencies updated—progress at pace! ✨

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately describes the main change: updating French (i18n/fr) documentation for beta29, which is reflected in both the removal of badge metadata from the 0-1-0-beta-28 guide and the addition of a new 0-1-0-beta-29 guide.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 6416a9e and 38f0565.

📒 Files selected for processing (2)

• src/content/docs/fr/guides/upgrade/version-guides/0-1-0-beta-28.mdx (0 hunks)
• src/content/docs/fr/guides/upgrade/version-guides/0-1-0-beta-29.mdx (1 hunks)

💤 Files with no reviewable changes (1)

• src/content/docs/fr/guides/upgrade/version-guides/0-1-0-beta-28.mdx

🧰 Additional context used

🧠 Learnings (2)

📓 Common learnings

Learnt from: ArmandPhilippot
Repo: withstudiocms/docs PR: 149
File: src/content/docs/fr/guides/upgrade/version-guides/0-1-0-beta-21.mdx:13-15
Timestamp: 2025-07-24T11:57:15.225Z
Learning: In the withstudiocms/docs repository, when reviewing French translation files, maintain consistency with the English version even if it means keeping unused imports. Structural parity between language versions is prioritized over removing unused code.

Learnt from: ArmandPhilippot
Repo: withstudiocms/docs PR: 149
File: src/content/docs/fr/guides/upgrade/version-guides/0-1-0-beta-20.mdx:18-18
Timestamp: 2025-07-24T12:00:35.014Z
Learning: In the withstudiocms/docs repository, while translations should maintain structural parity with English versions, improving readability during translation is acceptable when the original text has clear redundancy or readability issues that would also impact the translation quality. The maintainer ArmandPhilippot confirmed this approach is reasonable when the technical meaning is preserved.

Learnt from: ArmandPhilippot
Repo: withstudiocms/docs PR: 130
File: src/content/docs/fr/guides/upgrade/version-guides/0-1-0-beta-17.mdx:1-11
Timestamp: 2025-04-26T12:29:17.995Z
Learning: When reviewing translations in the withstudiocms/docs repository, compare with the corresponding English version as the source of truth, not with other files in the same target language. French translations should maintain structural parity with their English counterparts.

📚 Learning: 2025-07-24T11:57:15.225Z

Learnt from: ArmandPhilippot
Repo: withstudiocms/docs PR: 149
File: src/content/docs/fr/guides/upgrade/version-guides/0-1-0-beta-21.mdx:13-15
Timestamp: 2025-07-24T11:57:15.225Z
Learning: In the withstudiocms/docs repository, when reviewing French translation files, maintain consistency with the English version even if it means keeping unused imports. Structural parity between language versions is prioritized over removing unused code.

Applied to files:

• src/content/docs/fr/guides/upgrade/version-guides/0-1-0-beta-29.mdx

🪛 LanguageTool

src/content/docs/fr/guides/upgrade/version-guides/0-1-0-beta-29.mdx

[grammar] ~1-1: Il y a peut-être une erreur ici
Context: --- i18nReady: true title: "Mise à niveau : 0.1.0-beta.29" description: Mettre à niveau StudioCMS vers la version Beta.29 sidebar: label: 0.1.0-beta.29 badge: text: NOUVEAU variant: success order: 999986 --- import ReadMore from '/components/ReadM...

(QB_NEW_FR)

---

[grammar] ~15-~15: Il y a peut-être une erreur ici
Context: ...e } from '@astrojs/starlight/components' ## Corrections de bugs et améliorations - M...

(QB_NEW_FR)

---

[grammar] ~21-~21: Il y a peut-être une erreur ici
Context: ...es à jour vers leurs dernières versions.

(QB_NEW_FR)

🔇 Additional comments (3)

src/content/docs/fr/guides/upgrade/version-guides/0-1-0-beta-29.mdx (3)

13-15: No action needed—imports are intentional for parity with the English version.

The verification confirms that the English guide (the source of truth) contains identical imports (ReadMore and Aside) that are also unused in that version. This is consistent with repository learnings: structural parity between language versions is prioritized over removing unused imports. The French file correctly mirrors the English structure.

---

19-21: French translation is accurate and maintains structural parity with the English version.

Verification confirms:

• Line 20 correctly translates the @studiocms/ui version update and Picocolors bug fix; the phrasing is idiomatic and accurate
• Line 21 properly conveys "Updated various other dependencies to their latest versions" in natural French
• Both lines maintain structural parity with the English counterpart

No revisions needed.

---

1-11: Verification complete — structural parity confirmed with English beta-29 guide.

The file maintains proper structural parity with the English version:

• English beta-29 guide exists with identical structure and equivalent badge ("NEW" translated to "NOUVEAU")
• Version ordering (999986) aligns with version guide pattern
• Badge presence is intentional in beta-29 design (absent in beta-28, present in beta-29 for both languages)
• French translations are accurate ("Corrections de bugs et améliorations", "Mise à jour de @studiocms/ui vers la version...")
• Imports (ReadMore, Aside) are unused but consistent with the English source, maintaining parity per repository learnings

No issues identified.

---

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

• X
• Mastodon
• Reddit
• LinkedIn

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

[studiocms-no-reply]

Lunaria Status Overview

🌕 This pull request will trigger status changes.

Learn more

By default, every PR changing files present in the Lunaria configuration's files property will be considered and trigger status changes accordingly.

You can change this by adding one of the keywords present in the ignoreKeywords property in your Lunaria configuration file in the PR's title (ignoring all files) or by including a tracker directive in the merged commit's description.

Tracked Files

File	Note
fr/guides/upgrade/version-guides/0-1-0-beta-28.mdx	Localization changed, will be marked as complete.
fr/guides/upgrade/version-guides/0-1-0-beta-29.mdx	Localization added, will be marked as complete.

Warnings reference

Icon	Description
🔄️	The source for this localization has been updated since the creation of this pull request, make sure all changes in the source have been applied.

[dreyfus92]

merci @ArmandPhilippot 🤘🏻