i18n(fr): update beta30 docs

[ArmandPhilippot]

Description

Adds changes from #173 to the French translations (update beta29 to remove the badge and translate beta30).

Summary by CodeRabbit

• Documentation
  • Added version guide documentation for beta-30 release with French localization.
  • Documented bug fixes and improvements including setup script enhancements and dependency updates.
  • Updated sidebar navigation for beta-29 documentation.

[coderabbitai]

📝 Walkthrough

Walkthrough

French localization updates to upgrade guide documentation. Removes a badge from the 0.1.0-beta-29 guide frontmatter and adds a new 0.1.0-beta-30 version page documenting bug fixes and dependency updates.

Changes

Cohort / File(s)	Change Summary
French upgrade guide badge removal src/content/docs/fr/guides/upgrade/version-guides/0-1-0-beta-29.mdx	Removed the "NOUVEAU" badge (variant: success) from sidebar frontmatter metadata
French upgrade guide addition src/content/docs/fr/guides/upgrade/version-guides/0-1-0-beta-30.mdx	Added new documentation page with frontmatter, component imports (ReadMore, QuickUpdate, Aside), and a "Corrections de bugs et améliorations" section documenting setup script fixes and dependency updates

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

• The changes are cosmetic documentation updates in French localization files with no functional code logic changes
• Badge removal is a simple frontmatter edit
• New version guide follows established patterns in the documentation structure

Possibly related PRs

• i18n(fr): update beta29 docs #174: Modifies the same 0-1-0-beta-29 French guide file, adding the badge that this PR removes
• feat: add upgrade guide for StudioCMS Beta.30 #173: Applies equivalent documentation changes for French locale upgrade guides with badge removal and version page updates
• i18n(fr): update upgrade/versions-guides #152: Performs similar badge removal from frontmatter in French upgrade guide documentation files

Suggested labels

i18n

Suggested reviewers

• dreyfus92
• louisescher
• Adammatthiesen

Poem

🐰 A badge bid farewell, "NOUVEAU" no more,
A fresh guide appears through the documentation door,
Les français, they're updated with care,
Bug fixes and deps beyond compare! 📚✨

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: adding French (i18n/fr) documentation updates for beta30 with a related badge removal in beta29.
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 9b1ac93 and 535a2de.

📒 Files selected for processing (2)

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

💤 Files with no reviewable changes (1)

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

🧰 Additional context used

🧠 Learnings (1)

📓 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.

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)

• GitHub Check: Run Starlight Link Check

🔇 Additional comments (3)

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

1-11: Badge consistency is correct across versions and languages.

The verification confirms that the badge is intentionally and consistently present in both the French and English beta-30 guides, while both beta-29 guides have no badge. This is consistent design, not an error. No action required.

---

3-4: Translations verified as accurate.

The French translations match their English counterparts correctly in terminology, structure, and technical content. No issues found.

---

13-15: Structural parity confirmed—no changes needed.

The French version correctly mirrors the English version with identical imports and content structure. The unused imports (ReadMore and Aside) are present in both versions intentionally, maintaining the structural parity standard for this repository's translations.

---

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-29.mdx	Localization changed, will be marked as complete.
fr/guides/upgrade/version-guides/0-1-0-beta-30.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.