i18n(fr): update package-catalog#157
Conversation
WalkthroughThis update introduces new French documentation files for several StudioCMS plugins, including OAuth providers (Auth0, Discord, GitHub, Google), Markdown/MDX/Markdoc/HTML support, and updates to existing docs to clarify extension dependencies. Most changes add usage instructions, configuration examples, and required environment variables. Changes
Sequence Diagram(s)sequenceDiagram
participant User
participant StudioCMS Docs
User->>StudioCMS Docs: Access plugin documentation
StudioCMS Docs->>User: Show setup instructions, config, and env vars
User->>StudioCMS Docs: Follow steps to configure plugin
StudioCMS Docs->>User: Provide dependency and usage notes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~7 minutes Possibly related PRs
Suggested labels
Suggested reviewers
Poem
Note ⚡️ Unit Test Generation is now available in beta!Learn more here, or try it out under "Finishing Touches" below. ✨ Finishing Touches🧪 Generate unit tests
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. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
✅ Deploy Preview for studiocms-dev-docs ready!Built without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify project configuration. |
Lunaria Status Overview🌕 This pull request will trigger status changes. Learn moreBy default, every PR changing files present in the Lunaria configuration's You can change this by adding one of the keywords present in the Tracked Files
Warnings reference
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 0
🧹 Nitpick comments (13)
src/content/docs/fr/package-catalog/studiocms-plugins/studiocms-github.mdx (2)
13-14: Remove unnecessary NBSP before the semicolon.The thin non-breaking space just before
;trips some linters/formatters and is unnecessary.-import { PackageManagers } from 'starlight-package-managers' -import { Steps, Tabs, TabItem, Aside } from '@astrojs/starlight/components'; +import { PackageManagers } from 'starlight-package-managers' +import { Steps, Tabs, TabItem, Aside } from '@astrojs/starlight/components';
18-30: Add an installation snippet for parity with other plugin docs.Most plugin pages include a
<PackageManagers>ornpm/pnpmcommand before the configuration code. Including it keeps the French docs structurally aligned with the English originals and avoids readers wondering how to install the package.src/content/docs/fr/package-catalog/studiocms-plugins/studiocms-discord.mdx (2)
13-14: Unneeded thin space before semicolon.Same stylistic issue as in the GitHub page; consider removing the
before;to appease formatters.
18-30: Include an install command for consistency.Adding a
<PackageManagers>block (or annpm i @studiocms/discordexample) keeps this page consistent with other catalog entries.src/content/docs/fr/package-catalog/studiocms-plugins/studiocms-google.mdx (2)
13-14: Thin space before semicolon—minor cleanup.As with the other files, drop the fine NBSP before
;to avoid linter noise.
18-30: Consider adding an installation block.A short install command (or
<PackageManagers>) would align this page with the rest of the catalog.src/content/docs/fr/package-catalog/studiocms-plugins/studiocms-auth0.mdx (2)
13-14: Minor formatting: remove thin space before semicolon.Same comment as above; tiny but keeps formatting tools happy.
18-30: Add an installation example for completeness.Including a
<PackageManagers>block ornpm i @studiocms/auth0mirrors other docs and helps newcomers.src/content/docs/fr/package-catalog/studiocms-plugins/studiocms-markdoc.mdx (1)
14-14: Tiny formatting nit: extra NBSP before semicolon.Removing the fine non-breaking space keeps import lines uniform with other docs.
-import { Steps, Tabs, TabItem, Aside } from '@astrojs/starlight/components'; +import { Steps, Tabs, TabItem, Aside } from '@astrojs/starlight/components';src/content/docs/fr/package-catalog/studiocms-plugins/studiocms-blog.mdx (1)
14-14: Replace narrow no-break space before;with a regular spaceThe space just before the semicolon is a Unicode
U+202F(narrow no-break space).
Although ECMAScript treats it as whitespace, keeping only ASCII spaces in import
statements avoids invisible-character issues when copying or linting.-import { Steps, Tabs, TabItem, Aside } from '@astrojs/starlight/components’; +import { Steps, Tabs, TabItem, Aside } from '@astrojs/starlight/components';src/content/docs/fr/package-catalog/studiocms-plugins/studiocms-mdx.mdx (1)
14-14: Replace narrow no-break space before;with a regular spaceSame invisible
U+202Fcharacter as in the Blog doc; swap it for a normal
space to avoid hidden-char lint warnings.-import { Steps, Tabs, TabItem, Aside } from '@astrojs/starlight/components’; +import { Steps, Tabs, TabItem, Aside } from '@astrojs/starlight/components';src/content/docs/fr/package-catalog/studiocms-plugins/studiocms-html.mdx (1)
14-14: Swap the narrow no-break space for a normal spaceA
U+202Fsneaked in before the semicolon; replace with an ASCII space.-import { Steps, Tabs, TabItem } from '@astrojs/starlight/components’; +import { Steps, Tabs, TabItem } from '@astrojs/starlight/components';src/content/docs/fr/package-catalog/studiocms-plugins/studiocms-md.mdx (1)
14-14: Normalise whitespace in the import lineSame remark as above: remove the
U+202Fnarrow no-break space before the
semicolon.-import { Steps, Tabs, TabItem } from '@astrojs/starlight/components’; +import { Steps, Tabs, TabItem } from '@astrojs/starlight/components';
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (9)
src/content/docs/fr/package-catalog/studiocms-plugins/studiocms-auth0.mdx(1 hunks)src/content/docs/fr/package-catalog/studiocms-plugins/studiocms-blog.mdx(1 hunks)src/content/docs/fr/package-catalog/studiocms-plugins/studiocms-discord.mdx(1 hunks)src/content/docs/fr/package-catalog/studiocms-plugins/studiocms-github.mdx(1 hunks)src/content/docs/fr/package-catalog/studiocms-plugins/studiocms-google.mdx(1 hunks)src/content/docs/fr/package-catalog/studiocms-plugins/studiocms-html.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-md.mdx(1 hunks)src/content/docs/fr/package-catalog/studiocms-plugins/studiocms-mdx.mdx(1 hunks)
🧰 Additional context used
🧠 Learnings (2)
📓 Common learnings
Learnt from: ArmandPhilippot
PR: withstudiocms/docs#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
PR: withstudiocms/docs#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
PR: withstudiocms/docs#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.
Learnt from: ArmandPhilippot
PR: withstudiocms/docs#140
File: src/content/docs/fr/guides/upgrade/version-guides/0-1-0-beta-19.mdx:24-24
Timestamp: 2025-07-21T12:16:32.374Z
Learning: In the withstudiocms/docs repository, documentation URLs in the package-catalog may maintain legacy path names for stability and consistency across language versions, even when the actual package names have been updated. Always verify that corresponding files exist before flagging URLs as broken.
📚 Learning: 2025-07-21T12:16:32.374Z
Learnt from: ArmandPhilippot
PR: withstudiocms/docs#140
File: src/content/docs/fr/guides/upgrade/version-guides/0-1-0-beta-19.mdx:24-24
Timestamp: 2025-07-21T12:16:32.374Z
Learning: In the withstudiocms/docs repository, documentation URLs in the package-catalog may maintain legacy path names for stability and consistency across language versions, even when the actual package names have been updated. Always verify that corresponding files exist before flagging URLs as broken.
Applied to files:
src/content/docs/fr/package-catalog/studiocms-plugins/studiocms-markdoc.mdxsrc/content/docs/fr/package-catalog/studiocms-plugins/studiocms-github.mdxsrc/content/docs/fr/package-catalog/studiocms-plugins/studiocms-html.mdxsrc/content/docs/fr/package-catalog/studiocms-plugins/studiocms-md.mdx
🪛 LanguageTool
src/content/docs/fr/package-catalog/studiocms-plugins/studiocms-blog.mdx
[uncategorized] ~14-~14: Le point-virgule est précédé d’une espace fine insécable.
Context: ...de } from '@astrojs/starlight/components'; Ce module d’extension active les fonct...
(FRENCH_WHITESPACE)
src/content/docs/fr/package-catalog/studiocms-plugins/studiocms-markdoc.mdx
[uncategorized] ~14-~14: Le point-virgule est précédé d’une espace fine insécable.
Context: ...de } from '@astrojs/starlight/components'; # Présentation Ce module d’extension ...
(FRENCH_WHITESPACE)
src/content/docs/fr/package-catalog/studiocms-plugins/studiocms-mdx.mdx
[uncategorized] ~14-~14: Le point-virgule est précédé d’une espace fine insécable.
Context: ...de } from '@astrojs/starlight/components'; # Présentation Ce module d’extension ...
(FRENCH_WHITESPACE)
src/content/docs/fr/package-catalog/studiocms-plugins/studiocms-discord.mdx
[uncategorized] ~14-~14: Le point-virgule est précédé d’une espace fine insécable.
Context: ...de } from '@astrojs/starlight/components'; Ce module d’extension intègre Discord ...
(FRENCH_WHITESPACE)
[style] ~16-~16: Une autre expression peut sembler plus percutante.
Context: ... Ce module d’extension intègre Discord en tant que fournisseur d’authentification OAuth po...
(EN_TANT_QUE1)
[typographical] ~20-~20: Caractère d’apostrophe incorrect.
Context: ... dans votre configuration de StudioCMS. (studiocms.config.mjs) ```ts title="stu...
(APOS_INCORRECT)
src/content/docs/fr/package-catalog/studiocms-plugins/studiocms-github.mdx
[uncategorized] ~14-~14: Le point-virgule est précédé d’une espace fine insécable.
Context: ...de } from '@astrojs/starlight/components'; Ce module d’extension intègre GitHub e...
(FRENCH_WHITESPACE)
[style] ~16-~16: Une autre expression peut sembler plus percutante.
Context: ...; Ce module d’extension intègre GitHub en tant que fournisseur d’authentification OAuth po...
(EN_TANT_QUE1)
[typographical] ~20-~20: Caractère d’apostrophe incorrect.
Context: ... dans votre configuration de StudioCMS. (studiocms.config.mjs) ```ts title="stu...
(APOS_INCORRECT)
src/content/docs/fr/package-catalog/studiocms-plugins/studiocms-html.mdx
[uncategorized] ~14-~14: Le point-virgule est précédé d’une espace fine insécable.
Context: ...em } from '@astrojs/starlight/components'; # Présentation Ce module d’extension ...
(FRENCH_WHITESPACE)
src/content/docs/fr/package-catalog/studiocms-plugins/studiocms-google.mdx
[uncategorized] ~14-~14: Le point-virgule est précédé d’une espace fine insécable.
Context: ...de } from '@astrojs/starlight/components'; Ce module d’extension intègre l’authen...
(FRENCH_WHITESPACE)
[typographical] ~20-~20: Caractère d’apostrophe incorrect.
Context: ... dans votre configuration de StudioCMS. (studiocms.config.mjs) ```ts title="stu...
(APOS_INCORRECT)
src/content/docs/fr/package-catalog/studiocms-plugins/studiocms-auth0.mdx
[uncategorized] ~14-~14: Le point-virgule est précédé d’une espace fine insécable.
Context: ...de } from '@astrojs/starlight/components'; Ce module d’extension intègre Auth0 en...
(FRENCH_WHITESPACE)
[style] ~16-~16: Une autre expression peut sembler plus percutante.
Context: ...'; Ce module d’extension intègre Auth0 en tant que fournisseur OAuth pour StudioCMS, perme...
(EN_TANT_QUE1)
[typographical] ~20-~20: Caractère d’apostrophe incorrect.
Context: ... dans votre configuration de StudioCMS. (studiocms.config.mjs) ```ts title="stu...
(APOS_INCORRECT)
src/content/docs/fr/package-catalog/studiocms-plugins/studiocms-md.mdx
[uncategorized] ~14-~14: Le point-virgule est précédé d’une espace fine insécable.
Context: ...em } from '@astrojs/starlight/components'; # Présentation Ce module d’extension ...
(FRENCH_WHITESPACE)
⏰ 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). (4)
- GitHub Check: Redirect rules - studiocms-dev-docs
- GitHub Check: Header rules - studiocms-dev-docs
- GitHub Check: Pages changed - studiocms-dev-docs
- GitHub Check: Run Starlight Link Check
🔇 Additional comments (7)
src/content/docs/fr/package-catalog/studiocms-plugins/studiocms-github.mdx (1)
32-38: Confirm environment-variable prefixes match the actual package.Double-check that the plugin expects the
CMS_GITHUB_*variables (and not e.g.STUDIOCMS_GITHUB_*orGITHUB_OAUTH_*). Mismatched prefixes will cause silent auth failures.src/content/docs/fr/package-catalog/studiocms-plugins/studiocms-discord.mdx (1)
32-38: Validate the expected env-var names.Please verify the
CMS_DISCORD_*names against the plugin source / English doc so readers don’t end up with incorrect variables.src/content/docs/fr/package-catalog/studiocms-plugins/studiocms-google.mdx (1)
32-38: Re-check env-var naming for Google.Ensure
CMS_GOOGLE_*is what the plugin actually reads; otherwise users will be puzzled when OAuth fails.src/content/docs/fr/package-catalog/studiocms-plugins/studiocms-auth0.mdx (1)
32-38: Verify Auth0 env-var set matches the code.Confirm that the plugin expects exactly the four variables listed here (and the given prefixes). If it uses different keys (e.g.,
AUTH0_CLIENT_ID), update accordingly.src/content/docs/fr/package-catalog/studiocms-plugins/studiocms-markdoc.mdx (1)
20-22: LGTM – clear dependency notice added.The new
<Aside>block cleanly states the@studiocms/mdrequirement and matches the English doc. No further action needed.src/content/docs/fr/package-catalog/studiocms-plugins/studiocms-blog.mdx (1)
18-20: Nice addition clarifying the dependencyThe
<Aside>block makes the MD plugin requirement explicit for readers. 👍src/content/docs/fr/package-catalog/studiocms-plugins/studiocms-mdx.mdx (1)
20-22: Dependency note adds valuable contextGood call adding the
<Aside>to point to@studiocms/md.
3 participants
Description
Adds changes from #150 and #151 to the French translations of
packages-catalog:studiocms-blog.mdx,studiocms-markdoc.mdxandstudiocms-mdx.mdxstudiocms-auth0.mdx,studiocms-discord.mdx,studiocms-github.mdx,studiocms-google.mdx,studiocms-html.mdxandstudiocms-md.mdxI know this looks like a lot but most are short and very similar so I think they will be quick to review. 😅 But if you prefer, I can split next time!
Summary by CodeRabbit