i18n(fr): add markdown-remark.mdx & studiocms-ui.mdx

[ArmandPhilippot]

Description

Adds the French translations of ecosystem/packages/markdown-remark.mdx & ecosystem/packages/studiocms-ui.mdx added in #194 and updated in #210

Summary by CodeRabbit

• Documentation
  • Added French documentation for the markdown-remark integration, including overview, installation, Astro integration configuration, processor details, and usage examples.
  • Added French documentation for the StudioCMS UI library with an overview, metadata for i18n/cataloging, and links to further UI resources.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

📝 Walkthrough

Walkthrough

Two new French documentation pages were added under src/content/docs/fr/ecosystem/packages: a detailed guide for the @studiocms/markdown-remark integration and processor, and an introductory page for the @studiocms/ui library with links to public UI docs. (49 words)

Changes

Cohort / File(s)	Summary
French Ecosystem Documentation src/content/docs/fr/ecosystem/packages/markdown-remark.mdx, src/content/docs/fr/ecosystem/packages/studiocms-ui.mdx	Added two French docs pages. markdown-remark.mdx documents the integration and processor, installation, config options (injectCSS, components, markdown options like callouts.theme, autoLinkHeadings, sanitize), and usage examples for integration and direct rendering. studiocms-ui.mdx introduces @studiocms/ui and links to public UI docs.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~12 minutes

Suggested reviewers

• dreyfus92
• Adammatthiesen

Poem

🐰 Bonjour! J'ai sauté dans le code ce matin,
Des pages françaises, claires et câlines,
Markdown et UI chantent en duo,
Docs prêtes à fleurir comme un chapeau,
Vive l'i18n — et les carottes aussi! 🥕✨

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and specifically describes the main change: adding French translations for two documentation files related to markdown-remark and studiocms-ui packages.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.

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

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

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

---

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/ecosystem/packages/markdown-remark.mdx	Localization added, will be marked as complete.
fr/ecosystem/packages/studiocms-ui.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.

[coderabbitai]

Actionable comments posted: 1

🤖 Fix all issues with AI agents

In `@src/content/docs/fr/ecosystem/packages/markdown-remark.mdx`:
- Around line 107-112: The render call uses an invalid object literal for its
third argument: instead of the nested `{ $$result, {custom: Custom} }` you
should pass an object that includes $$result and a components property mapping
the tag name to the component (i.e., $$result plus components: { custom: Custom
}) so update the render invocation that references render and the Custom symbol
to use a components property wrapping the custom component map.