i18n(fr): add package-catalog translations#40
Conversation
WalkthroughThis pull request adds several new Markdown documentation files to the French package catalog for StudioCMS. The new entries detail the integration of various plugins—including web vitals, blog, devapps, markdoc, and mdx—by providing metadata, installation instructions (via Astro's package manager or manual methods), configuration examples, and usage details. A new index page is also introduced to organize and present both StudioCMS-created and community-created packages. Changes
Sequence Diagram(s)sequenceDiagram
participant Dev as Developer
participant Docs as Documentation
participant CLI as CLI/Package Manager
participant Config as Astro Config
participant Dash as StudioCMS Dashboard
Dev->>Docs: Open integration guide (web-vitals, blog, etc.)
Dev->>CLI: Execute installation commands
CLI->>Config: Update configuration with plugin settings
Config->>Dash: Load and activate new plugin configurations
Dash-->>Dev: Display updated functionality (routes, metrics, tools)
Poem
🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
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)
Other keywords and placeholders
CodeRabbit Configuration File (
|
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 (11)
src/content/docs/fr/package-catalog/studiocms-plugins/studiocms-mdx.mdx (1)
13-14: Import Statements and Minor Formatting Notes.
The imports forPackageManagersand the UI components are correctly included. Note the minor static analysis flag regarding spacing before the semicolon on line 14—confirm that this adheres to your project's style guidelines.🧰 Tools
🪛 LanguageTool
[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-blog.mdx (1)
13-14: Valid Imports with a Minor Formatting Observation.
The import statements forPackageManagersand components from@astrojs/starlight/componentsare appropriate. Please review the semicolon spacing as noted by static analysis to ensure stylistic consistency.🧰 Tools
🪛 LanguageTool
[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/index.mdx (1)
7-8: Import Statements with a Minor Styling Note.
The import of thePackageCatalogcomponent and theBadgecomponent is correct. Please verify the spacing before punctuation in line 8 per your formatting standards.🧰 Tools
🪛 LanguageTool
[uncategorized] ~8-~8: Le point-virgule est précédé d’une espace fine insécable.
Context: ...ge } from '@astrojs/starlight/components'; Le catalogue de paquets est une collec...(FRENCH_WHITESPACE)
src/content/docs/fr/package-catalog/studiocms-plugins/studiocms-markdoc.mdx (1)
13-14: Accurate Import Block with a Minor Spacing Observation.
The import statements are correct; however, please check the spacing before semicolons as flagged by static analysis to ensure alignment with project style guidelines.🧰 Tools
🪛 LanguageTool
[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/community-plugins/web-vitals.mdx (1)
13-17: Import Statements and Formatting Adjustments.
The required components are imported correctly. There are minor static analysis notes regarding whitespace (e.g., spacing before semicolons and within module paths) and potential anglicism adjustments on line 15. Please review these to align with your project’s style guidelines.🧰 Tools
🪛 LanguageTool
[uncategorized]
14-/asse...14: Le point-virgule est précédé d’une espace fine insécable./components/Gallery.astro'; import { webVitalsImages } from "
Context: ...Gallery from '(FRENCH_WHITESPACE)
[uncategorized]
15-/assets/index.ts"; import { St...15: Une espace doit être ajoutée entre ces deux mots ou intégrez ce nouveau mot à votre dictionnaire personnel./components/Gallery.astro'; import { webVitalsImages } from "
Context: ... '(MOTS_COLLES)
[style] ~15-
15: Alternatives possibles pour cet anglicisme :/assets/index.ts"; import { Steps, Tabs, TabIte...
Context: ...ro'; import { webVitalsImages } from "(FR_SIMPLE_REPLACE_ANGLICISM_PREMIUM_ASSETS)
[uncategorized] ~15-
15: Le point-virgule est précédé d’une espace fine insécable./assets/index.ts"; import { Steps, Tabs, TabItem } from '@...
Context: ...ebVitalsImages } from "(FRENCH_WHITESPACE)
[uncategorized] ~16-~16: Le point-virgule est précédé d’une espace fine insécable.
Context: ...em } from '@astrojs/starlight/components'; # Présentation Cette intégration Astr...(FRENCH_WHITESPACE)
src/content/docs/fr/package-catalog/studiocms-plugins/studiocms-devapps.mdx (6)
1-11: Frontmatter Metadata is Well-Structured.
The frontmatter correctly sets up the page’s metadata with keys likei18nReady,title,type,catalogEntry, anddescription. Ensure that any punctuation (such as apostrophes and quotation marks) conforms with your French typographical style guidelines.
13-14: Import Statements Are Correct.
The file importsPackageManagersfromstarlight-package-managersand UI components (Steps,Tabs,TabItem) from@astrojs/starlight/componentsappropriately. Verify that the semicolon usage (present on line 14) is consistent with your project’s style conventions.🧰 Tools
🪛 LanguageTool
[uncategorized] ~14-~14: Le point-virgule est précédé d’une espace fine insécable.
Context: ...em } from '@astrojs/starlight/components'; # Présentation Une collection d’outil...(FRENCH_WHITESPACE)
20-31: Installation – Méthode Astro Instructions Look Good.
The "Méthode Astro" tab is well-structured with clear step-by-step instructions. The use of<Tabs>and<TabItem>enhances readability. The commented-out<Steps>component is acceptable if you intend to revisit or enable it later; otherwise, consider removing it for a cleaner codebase.🧰 Tools
🪛 LanguageTool
[style] ~29-~29: Un autre mot peut sembler plus précis et percutant.
Context: ...o" args="add @studiocms/devapps" /> 2. Mettez à jour votre fichier de configuration comme in...(METTRE_A_JOUR)
57-60: Utilisation Section is Informative.
The note clarifying that the tools are only available duringastro devis clear. Consider rephrasing for a more formal tone if desired (see static analysis hint at ~59), though the current wording is understandable.🧰 Tools
🪛 LanguageTool
[style] ~59-~59: Dans un contexte formel, d’autres structures peuvent être utilisées pour enrichir votre style.
Context: ...astro dev` et ne seront pas disponibles pendant les déploiements en production ! ### E...(REP_PENDANT)
77-93: Options de Configuration Snippet is Detailed.
The section listing the configuration options fordevAppsis informative and well-organized. Note the static analysis hint at ~79 regarding the apostrophe character—verify that the typographical marks align with your style guidelines.🧰 Tools
🪛 LanguageTool
[typographical] ~79-~79: Caractère d’apostrophe incorrect.
Context: ... options disponibles pour l’intégrationdevApps, avec les valeurs par défaut affichées....(APOS_INCORRECT)
95-106: Visionneuse libSQL Description is Clear.
The description for the libSQL viewer tool effectively explains its purpose and lists the necessary environment variables. Again, check for consistent apostrophe usage (refer to static analysis hints at ~99 and ~103) to ensure it meets your style standards.🧰 Tools
🪛 LanguageTool
[typographical] ~99-~99: Caractère d’apostrophe incorrect.
Context: ...on à la base de données distante libSQL@astrojs/db. #### Conditions requises Les variabl...(APOS_INCORRECT)
[typographical] ~103-~103: Caractère d’apostrophe incorrect.
Context: ...sont définies (également utilisées pour@astrojs/db) : -ASTRO_DB_REMOTE_URL- **`AST...(APOS_INCORRECT)
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (6)
src/content/docs/fr/package-catalog/community-plugins/web-vitals.mdx(1 hunks)src/content/docs/fr/package-catalog/index.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-devapps.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)
🧰 Additional context used
🪛 LanguageTool
src/content/docs/fr/package-catalog/index.mdx
[uncategorized] ~8-~8: Le point-virgule est précédé d’une espace fine insécable.
Context: ...ge } from '@astrojs/starlight/components'; Le catalogue de paquets est une collec...
(FRENCH_WHITESPACE)
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: ...em } 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: ...em } from '@astrojs/starlight/components'; # Présentation Ce module d’extension ...
(FRENCH_WHITESPACE)
src/content/docs/fr/package-catalog/studiocms-plugins/studiocms-devapps.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 Une collection d’outil...
(FRENCH_WHITESPACE)
[style] ~29-~29: Un autre mot peut sembler plus précis et percutant.
Context: ...o" args="add @studiocms/devapps" /> 2. Mettez à jour votre fichier de configuration comme in...
(METTRE_A_JOUR)
[style] ~59-~59: Dans un contexte formel, d’autres structures peuvent être utilisées pour enrichir votre style.
Context: ...astro dev` et ne seront pas disponibles pendant les déploiements en production ! ### E...
(REP_PENDANT)
[typographical] ~79-~79: Caractère d’apostrophe incorrect.
Context: ... options disponibles pour l’intégration devApps, avec les valeurs par défaut affichées....
(APOS_INCORRECT)
[typographical] ~99-~99: Caractère d’apostrophe incorrect.
Context: ...on à la base de données distante libSQL @astrojs/db. #### Conditions requises Les variabl...
(APOS_INCORRECT)
[typographical] ~103-~103: Caractère d’apostrophe incorrect.
Context: ...sont définies (également utilisées pour @astrojs/db) : - ASTRO_DB_REMOTE_URL - **`AST...
(APOS_INCORRECT)
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: ...em } from '@astrojs/starlight/components'; # Présentation Ce module d’extension ...
(FRENCH_WHITESPACE)
src/content/docs/fr/package-catalog/community-plugins/web-vitals.mdx
[uncategorized] 14-/asse...14: Le point-virgule est précédé d’une espace fine insécable./components/Gallery.astro'; import { webVitalsImages } from "
Context: ...Gallery from '
(FRENCH_WHITESPACE)
[uncategorized] 15-/assets/index.ts"; import { St...15: Une espace doit être ajoutée entre ces deux mots ou intégrez ce nouveau mot à votre dictionnaire personnel./components/Gallery.astro'; import { webVitalsImages } from "
Context: ... '
(MOTS_COLLES)
[style] ~15-15: Alternatives possibles pour cet anglicisme :/assets/index.ts"; import { Steps, Tabs, TabIte...
Context: ...ro'; import { webVitalsImages } from "
(FR_SIMPLE_REPLACE_ANGLICISM_PREMIUM_ASSETS)
[uncategorized] ~15-15: Le point-virgule est précédé d’une espace fine insécable./assets/index.ts"; import { Steps, Tabs, TabItem } from '@...
Context: ...ebVitalsImages } from "
(FRENCH_WHITESPACE)
[uncategorized] ~16-~16: Le point-virgule est précédé d’une espace fine insécable.
Context: ...em } from '@astrojs/starlight/components'; # Présentation Cette intégration Astr...
(FRENCH_WHITESPACE)
[typographical] ~36-~36: Une espace est requise.
Context: ...push" /> {/* /} {/ */} 1. Install...
(DEUX_POINTS_ESPACE)
[uncategorized] ~44-~44: Le trait d’union doit être supprimé.
Context: ...kg="@astrojs/web-vitals" /> 2. Ajoutez @astrojs/web-vitals à votre fichier de configuration Astro...
(MOT_TRAIT_MOT)
🔇 Additional comments (18)
src/content/docs/fr/package-catalog/studiocms-plugins/studiocms-mdx.mdx (2)
1-11: Front Matter Metadata is Well Defined.
The YAML front matter clearly sets i18n readiness, title, type, catalog entry, description, and sidebar badge details. Please double-check that thecatalogEntryvalue aligns with naming conventions used elsewhere in the project if applicable.
16-38: Clear and Concise Content with Correct Installation Steps.
The presentation text and installation instructions are well written in French. The step-by-step guide with the embedded code snippet is clear and should be helpful for users.src/content/docs/fr/package-catalog/studiocms-plugins/studiocms-blog.mdx (2)
1-11: Well-Structured Front Matter.
The front matter correctly reflects the integration details for the StudioCMS blog, and the metadata is consistent with the other documentation entries.
16-48: Detailed Presentation and Installation Instructions.
The content provides a clear description of the module’s purpose and offers detailed instructions for installation, including a configuration snippet. The layout is user friendly and should aid in setup.src/content/docs/fr/package-catalog/index.mdx (2)
1-5: Properly Configured Front Matter.
The YAML front matter is clear, marking the file as i18n-ready and providing a concise title and description for the package catalog page.
10-27: Content Clarity and Component Integration.
The description of the package catalog is clear, and the usage of the<Badge>and<PackageCatalog>components is demonstrated effectively. The instructional text is precise and should guide users well.src/content/docs/fr/package-catalog/studiocms-plugins/studiocms-markdoc.mdx (2)
1-11: Well-Formatted Metadata Block.
The front matter is complete and clearly establishes the context for the@studiocms/markdocintegration. This provides a solid starting point for the documentation.
16-38: Clear Presentation and Installation Guideline.
The installation instructions and the accompanying configuration example are clear and well-ordered, making it straightforward for users to set up the MarkDoc integration.src/content/docs/fr/package-catalog/community-plugins/web-vitals.mdx (2)
1-11: Front Matter Accurately Conveys Integration Details.
The metadata block effectively communicates that this integration is for@astrojs/web-vitals, with all necessary fields and a proper sidebar badge.
18-79: Comprehensive Installation Instructions and Layout.
The documentation provides a detailed presentation of the integration, including a tabbed installation section that outlines both the Astro and manual methods. The code snippets and instructions are clearly delineated, and the commented-out gallery section is a useful placeholder for future enhancements.🧰 Tools
🪛 LanguageTool
[typographical] ~36-~36: Une espace est requise.
Context: ...push" /> {/* /} {/ */} 1. Install...(DEUX_POINTS_ESPACE)
[uncategorized] ~44-~44: Le trait d’union doit être supprimé.
Context: ...kg="@astrojs/web-vitals" /> 2. Ajoutez@astrojs/web-vitalsà votre fichier de configuration Astro...(MOT_TRAIT_MOT)
src/content/docs/fr/package-catalog/studiocms-plugins/studiocms-devapps.mdx (8)
16-19: Présentation Section is Clear.
The introductory section succinctly explains the purpose of the integration in French. The translation is clear and effective.
32-39: Installation – Méthode Manuelle is Well-Documented.
The manual installation steps are straightforward and include clear instructions on installing the package and updating the Astro configuration. The use of inline code snippets is appropriate.
40-52: Configuration Code Block is Correct.
The embedded code snippet (labelled asastro.config.mjs) clearly demonstrates how to integrate@studiocms/devappsinto the Astro configuration using the manual method. The inline annotation (ins={3, 9}) is correctly applied.
61-75: Exemple de Configuration is Well-Structured.
The configuration example is concise and demonstrates the integration effectively using ats twoslashcode block. It provides clear guidance on integrating the package.
107-112: Aperçu de l’Utilisation – LibSQL Viewer (Fermée) is Clear.
The preview image for the closed toolbar application is properly referenced and provides users with a visual understanding of the tool.
113-116: Aperçu de l’Utilisation – LibSQL Viewer (Étendue) is Effective.
The image showing the expanded toolbar application is clearly included, enhancing the documentation’s clarity.
117-125: Importateur Wordpress Section is Comprehensive.
The explanation for the WordPress importer tool is complete and lists all prerequisites clearly. The translation accurately reflects the functionality and requirements.
127-132: Aperçu de l’Utilisation – Importateur Wordpress is Well-Presented.
The preview image for the WordPress importer tool assists in visualizing the tool’s interface. The documentation in this section is consistent and clear.
dreyfus92
left a comment
dreyfus92
left a comment
There was a problem hiding this comment.
Merci beaucoup @ArmandPhilippot pour ce travail formidable ! 😄
3 participants
Description
Adds the French translation of
package-catalogpages.Summary by CodeRabbit