i18n(fr): update package-catalog

[ArmandPhilippot]

Description

Adds changes from #73 and #106 to the French translation of package-catalog files.

Summary by CodeRabbit

• Documentation
  • Updated package catalog documentation to clarify the "Experimental" label for extension modules.
  • Improved installation instructions and configuration wording for @studiocms/blog, @studiocms/markdoc, and @studiocms/mdx packages for better clarity and explicit command usage.

[coderabbitai]

Warning

Rate limit exceeded

@ArmandPhilippot has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 22 minutes and 59 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

📥 Commits

Reviewing files that changed from the base of the PR and between 26d5619 and 91ed02a.

📒 Files selected for processing (3)

• src/content/docs/fr/package-catalog/studiocms-plugins/studiocms-blog.mdx (1 hunks)
• src/content/docs/fr/package-catalog/studiocms-plugins/studiocms-markdoc.mdx (1 hunks)
• src/content/docs/fr/package-catalog/studiocms-plugins/studiocms-mdx.mdx (1 hunks)

Walkthrough

The updates focus on the French documentation for the package catalog and StudioCMS plugins. They add an explanation about the "Experimental" badge for extension modules, clarifying its meaning and implications. Additionally, installation instructions for several StudioCMS plugins are revised to use a more explicit command format with the <PackageManagers> component, and the configuration step wording is updated for clarity. No changes are made to any exported or public entities.

Changes

Files	Change Summary
src/content/docs/fr/package-catalog/index.mdx	Added explanation about "Experimental" badge for extension modules, clarifying its significance and usage.
src/content/docs/fr/package-catalog/studiocms-plugins/studiocms-blog.mdx, src/content/docs/fr/package-catalog/studiocms-plugins/studiocms-markdoc.mdx, src/content/docs/fr/package-catalog/studiocms-plugins/studiocms-mdx.mdx	Updated installation instructions for StudioCMS plugins to use explicit <PackageManagers> command format and clarified configuration step wording.

Possibly related PRs

• i18n(fr): add package-catalog translations #40: Adds French translations and documentation for the package catalog and plugins, directly related to the same files and content.
• i18n(ko-KR): update package-catalog/ and index.mdx #97: Updates the same documentation files for package catalog and plugins in Korean, mirroring the changes made in French.
• i18n(es): update /package-catalog/ #112: Also adds the "Experimental" badge explanation and explicit installation instructions, directly overlapping in scope.

Suggested labels

i18n

Suggested reviewers

• dreyfus92

Poem

In burrows deep, a rabbit found,
New badges and commands abound!
French docs now clearly show,
How StudioCMS plugins grow.
"Experimental"—a badge to see,
Install with care, then hop with glee!
🐇📦✨

---

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

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[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/package-catalog/index.mdx	Localization changed, will be marked as complete.
fr/package-catalog/studiocms-plugins/studiocms-blog.mdx	Localization changed, will be marked as complete.
fr/package-catalog/studiocms-plugins/studiocms-markdoc.mdx	Localization changed, will be marked as complete.
fr/package-catalog/studiocms-plugins/studiocms-mdx.mdx	Localization changed, 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.