i18n(fr): update how-it-works/cli#122
Conversation
WalkthroughThe updates focus on the French documentation for StudioCMS, particularly the CLI tools. The CLI documentation is extensively expanded and reorganized, introducing a new CLI tool, clarifying command usage, and providing comprehensive examples and navigation enhancements. Additionally, a link in the French "getting started" guide is updated to reference the French upgrade guide instead of the English one. No changes are made to code or exported entities. Changes
Sequence Diagram(s)sequenceDiagram
participant User
participant Docs
User->>Docs: Accesses CLI documentation (French)
Docs-->>User: Presents expanded, organized CLI tool info with usage examples
User->>Docs: Accesses "Getting Started" guide
Docs-->>User: Provides link to French upgrade guide
Possibly related PRs
Suggested labels
Suggested reviewers
Poem
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:
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 (2)
src/content/docs/fr/how-it-works/cli.mdx (2)
314-314: Nitpick: Capitalize heading "Étiquette"
In French headings, capitalize the first letter. Change to:#### Étiquette (facultatif)
315-315: Refine phrasing for tag option
Consider tightening the sentence for clarity, e.g.:Spécifier une étiquette (
tag) pour la résolution des paquets ; si aucune n’est fournie,@studiocms-upgradeutilise la plus récente.🧰 Tools
🪛 LanguageTool
[typographical] ~315-~315: Caractère d’apostrophe incorrect.
Context: ...Il est possible de passer une étiquette (tag) spécifique pour résoudre les paque...(APOS_INCORRECT)
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (2)
src/content/docs/fr/how-it-works/cli.mdx(4 hunks)src/content/docs/fr/start-here/getting-started.mdx(1 hunks)
🧰 Additional context used
🪛 LanguageTool
src/content/docs/fr/how-it-works/cli.mdx
[uncategorized] ~15-15: Le point-virgule est précédé d’une espace fine insécable./components/Read...
Context: ...em } from '@astrojs/starlight/components'; import ReadMore from '
(FRENCH_WHITESPACE)
[uncategorized] ~16-16: Le point-virgule est précédé d’une espace fine insécable./components/ReadMore.astro'; Les interfaces en ligne de commandes (...
Context: ...adMore from '
(FRENCH_WHITESPACE)
[uncategorized] ~121-~121: Une de ces ponctuations est superflue.
Context: ...a [documentation][turso-docs] de Turso :::note Windows nécessite l’utilisation de...
(grammalecte_typo_ponctuation_superflue3)
[typographical] ~122-~122: Une espace est requise.
Context: ...[documentation][turso-docs] de Turso :::note Windows nécessite l’utilisation de ...
(DEUX_POINTS_ESPACE)
[uncategorized] ~123-~123: Les deux-points sont précédés d’une espace insécable.
Context: ...essite l’utilisation de WSL selon Turso ::: ```log Utilisation : getTurso [option...
(FRENCH_WHITESPACE)
[typographical] ~151-~151: Il manque une espace après le point.
Context: ...nfigurez votre fichier d’environnement (.env) avec des options pour : - Utiliser ...
(ESPACE_APRES_POINT)
[uncategorized] ~152-~152: Ce mot doit commencer par une minuscule.
Context: ...ent (.env) avec des options pour : - Utiliser un exemple de modèle .env - Utilis...
(DEUX_POINTS_MAJ)
[typographical] ~153-~153: Il manque une espace après le point.
Context: ... - Utiliser le générateur interactif .env qui peut : - Configurer une nouve...
(ESPACE_APRES_POINT)
[uncategorized] ~154-~154: Ce mot doit commencer par une minuscule.
Context: ...eur interactif .env qui peut : - Configurer une nouvelle base de données Turso (si ...
(DEUX_POINTS_MAJ)
[style] ~159-~159: Cette structure peut être allégée afin de devenir plus percutante.
Context: ...ique de Turso CLI et l’authentification si nécessaire lors de la configuration d’une base de donné...
(SI_POSSIBLE1)
[uncategorized] ~161-~161: S’il s’agit d’un impératif, mettez un trait d’union.
Context: ...complète des variables d’environnement, consultez la [documentation des variables d’environn...
(grammalecte_gv1__imp_union_le_la_leur__b1_a1_1)
[style] ~289-~289: Une autre structure plus directe dynamisera votre phrase.
Context: ...ntégrations officielles du projet Astro en même temps que vous mettez à niveau StudioCMS. ##...
(EN_MEME_TEMPS1)
[typographical] ~315-~315: Caractère d’apostrophe incorrect.
Context: ...Il est possible de passer une étiquette (tag) spécifique pour résoudre les paque...
(APOS_INCORRECT)
⏰ Context from checks skipped due to timeout of 90000ms (1)
- GitHub Check: Run Starlight Link Check
🔇 Additional comments (11)
src/content/docs/fr/start-here/getting-started.mdx (1)
15-15: Update French upgrade guide link
TheLinkCardnow correctly points to/fr/guides/upgrade/latest/instead of the English version—this aligns the “Mise à niveau” card with the French documentation.src/content/docs/fr/how-it-works/cli.mdx (10)
7-9: Add "Mis à jour" badge in frontmatter
The new badge signals that this page has been recently updated in the sidebar—good for discoverability.
10-12: Configure table of contents
AddingtableOfContentswithminHeadingLevel: 2andmaxHeadingLevel: 4will generate an in-page index for headings H2–H4, improving navigation in this long document.
20-24: Include new CLI tool "@studiocms/upgrade"
The list of CLI utilities is correctly expanded to include@studiocms/upgrade. The anchor#studiocms-upgradematches the section heading below.
28-30: Standardize French section headings
The translated heading### Options et commandes complètes de la CLIunder thestudiocmssection is clear and consistent with French documentation style.
176-176: Align create‑studiocms section heading
Using the same### Options et commandes complètes de la CLIheading in thecreate‑studiocmssection maintains consistency across CLI docs.
239-239: Clarify command overview
The new heading### Présentation des commandessuccinctly introduces the list of commands in thecreate‑studiocmssection.
269-269: Improve Turso installation instruction
The sentence clearly directs users to Turso’s official documentation for installation—concise and accurate.
285-285: Introduce new@studiocms-upgradetool
This new section properly names and describes the upgrade CLI utility, matching the entry in the list of tools above.
291-291: Consistent example usage heading
### Exemple d'utilisationmirrors other sections, making the pattern predictable for readers.
311-311: Options heading
The### Optionsheading correctly scopes the list of flags for@studiocms-upgrade.
3 participants
Description
how-it-works/cli.mdx.start-here/getting-started.mdx(I missed that in i18n(fr): updateindexandstart-here/getting-started#120)Summary by CodeRabbit
@studiocms-upgradeCLI.