fix: restructure French docs to match other locales (fr/docs/ path)

[Pitiakova]

Problem

The French locale had all docs content at fr/ root level (e.g. fr/live-updates/, fr/getting-started/), while all other locales store content under fr/docs/ (e.g. de/docs/live-updates/, es/docs/live-updates/).

Starlight routes /fr/docs/live-updates/features/ to fr/docs/live-updates/features.mdx, not fr/live-updates/features.mdx, so all French pages were falling back to English.

This also caused the entire left sidebar to show in English for all French docs pages.

Changes

• Copied all French content from fr/ to fr/docs/ to match the structure of de, es, id, it, ja, ko, zh locales
• Sections moved: getting-started, cli, live-updates, plugins, public-api, upgrade, webapp, plugin, contributing
• Files moved: faq.mdx, getting-help.mdx, how-to.mdx, index.mdx
• Fixed locale: fr field position to be first in frontmatter for features.mdx and update-types.mdx
• Fixed sidebar ordering for update-types (order: 4) and integrations (order: 3) in French live-updates

Result

• French sidebar now shows all items in French
• French Features page renders in French
• French docs follow same structure as all other locales (268 files)

Made with Cursor

Summary by CodeRabbit

• Documentation
  • Added comprehensive French-language documentation including FAQ, getting help guide, and how-to tutorials.
  • Added detailed French documentation for live updates features: channels, encryption, custom storage, compliance, China configuration, rollbacks, and update behavior.
  • Added French CI/CD integration guides for Azure DevOps, GitHub Actions, GitLab CI, and Bitbucket Pipelines.

[coderabbitai]

📝 Walkthrough

Walkthrough

This PR adds comprehensive French-language documentation to Capgo, introducing 19+ new MDX and Markdown files covering FAQ, getting started guides, live updates features (channels, encryption, custom storage, compliance), CI/CD integrations (Azure DevOps, Bitbucket, GitHub Actions, GitLab), and update behavior, alongside minor formatting fixes to existing French documentation files.

Changes

Cohort / File(s)	Summary
Core French Documentation src/content/docs/fr/docs/faq.mdx, src/content/docs/fr/docs/getting-help.mdx, src/content/docs/fr/docs/how-to.mdx, src/content/docs/fr/docs/index.mdx	Added foundational French documentation pages including FAQ (Code Push, bundles, roadmap, CI usage, stores), getting help (Discord/email support), how-to guides with LinkCard navigation, and localized index with featured sections and quick links.
Live Updates Core src/content/docs/fr/docs/live-updates/.../{breaking-changes,channels,china-configuration,compliance,custom-storage,differentials,encryption,rollbacks,update-behavior}.md*	Comprehensive French live updates documentation covering update channels, versioning, regional configuration, privacy/compliance, custom storage options, differential updates, end-to-end encryption, rollback procedures, and update behavior customization with code examples and configuration guidance.
CI/CD Integrations src/content/docs/fr/docs/live-updates/integrations/{azure-devops,bitbucket-pipeline,github-actions,gitlab-ci,index}.mdx	Added detailed French integration guides for major CI/CD platforms (Azure DevOps, Bitbucket, GitHub Actions, GitLab) with pipeline examples, multi-channel deployments, security practices, monitoring setup, and an integrations index page.
Frontmatter Fixes src/content/docs/fr/live-updates/features.mdx, src/content/docs/fr/live-updates/update-types.mdx	Minor formatting adjustments to YAML frontmatter: moved locale field to top of block in features.mdx and restructured description formatting in update-types.mdx.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~25 minutes

Possibly related PRs

• Add comprehensive Live Update features documentation #478: Overlaps with French live-updates documentation additions (update-types.mdx, features.mdx) and sidebar ordering changes.
• fix: translation sidebar orders and French locale files #485: Concurrent French live-updates documentation modifications and locale folder structure adjustments.
• fix: move French features.mdx to correct path and fix sidebar ordering #491: Related directory structure changes and duplicate file removals in the same French docs/live-updates hierarchy.

Suggested labels

💰 Rewarded

Poem

🐰 With whiskers twitching and pride so bright,
French docs now shine with proper light,
From FAQ to CI, encryption's key,
Updates flow in French—c'est magnifique, vraiment! ✨

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and concisely summarizes the main change: restructuring French documentation to move files from fr/ to fr/docs/ path to align with other locale structures.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

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

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch fix/fr-features-path

---

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.}

[riderx]

@ToriChanIntegration please fix the merge conflict on the branch

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[coderabbitai]

Actionable comments posted: 18

Note

Due to the large number of review comments, Critical, Major severity comments were prioritized as inline comments.

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (2)

src/content/docs/fr/live-updates/features.mdx (2)

299-299: ⚠️ Potential issue | 🟡 Minor

Typo: l.integrité → l'intégrité

The period is used instead of an apostrophe in "vérifier l.integrité".

✏️ Proposed fix

-### Signature du code
-Vérifiez l.integrité du bundle avec des signatures cryptographiques pour prévenir toute altération.
+### Signature du code
+Vérifiez l'intégrité du bundle avec des signatures cryptographiques pour prévenir toute altération.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@src/content/docs/fr/live-updates/features.mdx` at line 299, Fix the typo in
the sentence containing "Vérifiez l.integrité du bundle avec des signatures
cryptographiques pour prévenir toute altération." by replacing the period with
an apostrophe so it reads "Vérifiez l'intégrité du bundle..." — update the
string in the same content block (the sentence starting with "Vérifiez
l.integrité") to use the correct character.

---

325-325: ⚠️ Potential issue | 🟡 Minor

Missing space before **Emplacement :**

Line 325 runs the sentence and the location marker together: ...l'organisation.**Emplacement :**. Add a line break or space.

✏️ Proposed fix

-Exiger que tous les bundles soient chiffrés au niveau de l'organisation.**Emplacement :** Web Dashboard → Organization → Security
+Exiger que tous les bundles soient chiffrés au niveau de l'organisation.
+
+**Emplacement :** Web Dashboard → Organization → Security

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@src/content/docs/fr/live-updates/features.mdx` at line 325, The sentence and
the location marker are run together; update the document content where the
string "Exiger que tous les bundles soient chiffrés au niveau de
l'organisation.**Emplacement :** Web Dashboard → Organization → Security"
appears so there is a space or a line break before "**Emplacement :**" (e.g.,
"...l'organisation. **Emplacement :** ..." or place "**Emplacement :** Web
Dashboard..." on the next line) to separate the sentence from the location
marker.

♻️ Duplicate comments (3)

src/content/docs/fr/docs/live-updates/china-configuration.mdx (1)

198-198: The same broken links (Support@capgo.Application, discord.capgo.Application) appear again in the troubleshooting section. Apply the same fix as described above.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@src/content/docs/fr/docs/live-updates/china-configuration.mdx` at line 198,
Replace the broken links in the troubleshooting sentence by updating the visible
and target link texts: change "Support@capgo.Application" to the correct support
email (e.g., "Support@capgo.app") and change "https://discord.capgo.Application"
(and the visible "discord.capgo.Application") to the correct Discord invite URL
(e.g., "https://discord.capgo.app"); update the mailto: and href values
accordingly so both the display text and link targets match the corrected
domains.

src/content/docs/fr/docs/getting-help.mdx (1)

11-11: Same domain normalization issue as noted in FAQ.

Also applies to: 42-42

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@src/content/docs/fr/docs/getting-help.mdx` at line 11, The markdown link uses
a mis-cased domain ("https://discord.capgo.Application") causing inconsistent
normalization; update the URL to the correctly cased canonical domain (e.g.,
replace "https://discord.capgo.Application" with
"https://discord.capgo.application" or the canonical domain used elsewhere) and
make the same change for the duplicate occurrence of that URL in the file so all
links match.

src/content/docs/fr/docs/live-updates/custom-storage.mdx (1)

300-302: Same internal-link slug issue as noted earlier.

The links under “Suivant Steps” use paths with spaces/accents (e.g., /docs/live-Mises à jour/...) and are likely to 404 unless matching slugs exist. Please normalize alongside the other FR doc links.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@src/content/docs/fr/docs/live-updates/custom-storage.mdx` around lines 300 -
302, The three internal links in the "Suivant Steps" list (link texts "Canaux",
"Mise à jour Behavior", "CI/CD Integration") use paths with spaces/accents and
will 404; update their hrefs to the normalized slugs used across the FR
docs—e.g. replace "/docs/live-Mises à jour/Canaux/" and "/docs/live-Mises à
jour/Mise à jour-behavior/" with the normalized live-updates slugs (e.g.
"/docs/live-updates/channels/" and "/docs/live-updates/update-behavior/") and
ensure "/docs/getting-started/cicd-integration/" uses the exact existing slug
for CI/CD integration so all three internal links match the canonical FR doc
slugs.

🟡 Minor comments (10)

src/content/docs/fr/docs/live-updates/encryption.mdx-323-323 (1)

323-323: ⚠️ Potential issue | 🟡 Minor

Mixed British/American spelling: "Organisation" vs "organization"

"SOC 2 (Service Organisation Control 2)" uses British spelling while the rest of the file uses American English ("organization"). The official name of SOC 2 uses "Organization".

✏️ Proposed fix

-- SOC 2 (Service Organisation Control 2)
+- SOC 2 (Service Organization Control 2)

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@src/content/docs/fr/docs/live-updates/encryption.mdx` at line 323, Replace
the British spelling in the SOC 2 label so it matches American English used
elsewhere: update the string "SOC 2 (Service Organisation Control 2)" to "SOC 2
(Service Organization Control 2)" in the document (search for the exact phrase
"SOC 2 (Service Organisation Control 2)").

src/content/docs/fr/docs/live-updates/rollbacks.mdx-74-74 (1)

74-74: ⚠️ Potential issue | 🟡 Minor

Journal in is not a valid phrase

"Journal in to the [Capgo Tableau de bord]" — "Journal" is not a verb in English. This appears to be a mistranslation. Should be "Log in to the [Capgo Dashboard]" (or the French equivalent "Connectez-vous au [Tableau de bord Capgo]" once the content is properly translated).

✏️ Proposed fix (English)

-1. Journal in to the [Capgo Tableau de bord](https://Application.capgo.io).
+1. Log in to the [Capgo Dashboard](https://app.capgo.io).

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@src/content/docs/fr/docs/live-updates/rollbacks.mdx` at line 74, The phrase
"Journal in to the [Capgo Tableau de bord]" is incorrect English; replace that
exact string with the correct English text "Log in to the [Capgo Dashboard]" (or
if the file is intended to be French, use "Connectez-vous au [Tableau de bord
Capgo]") by updating the content in
src/content/docs/fr/docs/live-updates/rollbacks.mdx where the text "Journal in
to the [Capgo Tableau de bord]" appears.

src/content/docs/fr/docs/live-updates/differentials.mdx-35-38 (1)

35-38: ⚠️ Potential issue | 🟡 Minor

Missing code example for enabling differential updates

The section heading "Enabling Differential Mises à jour" ends with the sentence "simply use the --partial flag when uploading a new version:" but is immediately followed by the next section header with no code block. The example command is absent.

✏️ Proposed addition

 To enable differential updates for your Capgo app, simply use the `--partial` flag when uploading a new version:

+```shell
+npx `@capgo/cli`@latest bundle upload --partial
+```
+
 ## Enforcing Differential Mises à jour

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@src/content/docs/fr/docs/live-updates/differentials.mdx` around lines 35 -
38, Add the missing example command for the "Enabling Differential Mises à jour"
section by inserting a fenced code block showing how to upload a new version
with the --partial flag; specifically add a shell code block containing the
suggested command (e.g., npx `@capgo/cli`@latest bundle upload --partial)
immediately after the sentence that mentions `--partial` so the heading
"Enabling Differential Mises à jour" includes an executable example before the
next section "Enforcing Differential Mises à jour".

src/content/docs/fr/docs/live-updates/integrations/github-actions.mdx-62-85 (1)

62-85: ⚠️ Potential issue | 🟡 Minor

Fix YAML indentation in the "Deploy to Capgo" step.

The run and env fields under the "Deploy to Capgo" step are incorrectly indented. This is the only issue; the action versions actions/checkout@v6 and actions/setup-node@v6 are correct and represent the current major versions as of January 2026.

Indentation fix

      - name: Deploy to Capgo
-       run: |
-         npm install -g `@capgo/cli`
-         npx `@capgo/cli` bundle upload --channel production
-        env:
-          CAPGO_TOKEN: ${{ secrets.CAPGO_TOKEN }}
-       # For encrypted uploads, add: --key-data-v2 "${{ secrets.CAPGO_PRIVATE_KEY }}"
+       run: |
+         npm install -g `@capgo/cli`
+         npx `@capgo/cli` bundle upload --channel production
+       env:
+         CAPGO_TOKEN: ${{ secrets.CAPGO_TOKEN }}
+       # For encrypted uploads, add: --key-data-v2 "${{ secrets.CAPGO_PRIVATE_KEY }}"

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@src/content/docs/fr/docs/live-updates/integrations/github-actions.mdx` around
lines 62 - 85, The "Deploy to Capgo" GitHub Actions step has incorrect YAML
indentation for the run and env keys in the step titled "Deploy to Capgo"; fix
it by aligning the run: and env: keys at the same indentation level as name: and
uses:, ensure the shell block under run has its commands indented one level
deeper, and place CAPGO_TOKEN under env as a mapping (CAPGO_TOKEN: ${{
secrets.CAPGO_TOKEN }}); verify there are no extra leading spaces before run and
that the comment about --key-data-v2 remains properly indented under env or the
run block as appropriate.

src/content/docs/fr/docs/live-updates/integrations/index.mdx-78-80 (1)

78-80: ⚠️ Potential issue | 🟡 Minor

Invalid URL paths in Related Documentation section.

Same broken live-Mises à jour pattern applies here:

Broken	Correct
/docs/live-Mises à jour/Canaux/	/docs/live-updates/channels/
/docs/live-Mises à jour/Chiffrement/	/docs/live-updates/encryption/
/docs/live-Mises à jour/Mise à jour-behavior/	/docs/live-updates/update-behavior/

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@src/content/docs/fr/docs/live-updates/integrations/index.mdx` around lines 78
- 80, The Related Documentation links use incorrect localized paths; update the
hrefs for the link texts [Canaux], [Chiffrement], and [Mise à jour Behavior] so
they point to the correct English-slugged routes: replace '/docs/live-Mises à
jour/Canaux/' with '/docs/live-updates/channels/', '/docs/live-Mises à
jour/Chiffrement/' with '/docs/live-updates/encryption/', and '/docs/live-Mises
à jour/Mise à jour-behavior/' with '/docs/live-updates/update-behavior/' in the
index.mdx content.

src/content/docs/fr/docs/live-updates/integrations/azure-devops.mdx-136-136 (1)

136-136: ⚠️ Potential issue | 🟡 Minor

Invalid URL paths — spaces in path segments will cause 404s.

The links below contain raw French text with spaces in the URL path (live-Mises à jour, Mise à jour-behavior). URL paths cannot contain unencoded spaces, and even if percent-encoded they won't match any actual route since the underlying pages live under live-updates/.

Affected lines and their corrected equivalents:

Broken	Correct
/docs/live-Mises à jour/Chiffrement/	/docs/live-updates/encryption/
/docs/live-Mises à jour/Chiffrement/#setting-up-Chiffrement	/docs/live-updates/encryption/#setting-up-encryption
/docs/live-Mises à jour/Canaux/	/docs/live-updates/channels/
/docs/live-Mises à jour/custom-storage/	/docs/live-updates/custom-storage/
/docs/live-Mises à jour/Mise à jour-behavior/	/docs/live-updates/update-behavior/

The same pattern appears in gitlab-ci.mdx, bitbucket-pipeline.mdx, and index.mdx — all affected files need the same fix.

Also applies to: 138-138, 166-166, 579-582

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@src/content/docs/fr/docs/live-updates/integrations/azure-devops.mdx` at line
136, Replace the invalid French URL path segments that contain spaces with the
correct English route segments in this file (and similarly in gitlab-ci.mdx,
bitbucket-pipeline.mdx, and index.mdx): update occurrences of "/docs/live-Mises
à jour/Chiffrement/" -> "/docs/live-updates/encryption/", "/docs/live-Mises à
jour/Chiffrement/#setting-up-Chiffrement" ->
"/docs/live-updates/encryption/#setting-up-encryption", "/docs/live-Mises à
jour/Canaux/" -> "/docs/live-updates/channels/", "/docs/live-Mises à
jour/custom-storage/" -> "/docs/live-updates/custom-storage/", and
"/docs/live-Mises à jour/Mise à jour-behavior/" ->
"/docs/live-updates/update-behavior/"; search for the exact broken strings in
azure-devops.mdx (lines near the shown instances) and replace them so links
point to the existing /docs/live-updates/* routes.

src/content/docs/fr/docs/live-updates/integrations/bitbucket-pipeline.mdx-468-489 (1)

468-489: ⚠️ Potential issue | 🟡 Minor

Misleading "Pipeline Validation" section — options.docker and size are runner settings, not validation.

The options.docker: true / size: 2x block configures Docker layer caching and doubles compute resources; it has nothing to do with catching configuration errors. The script body (echo "Pipeline validation successful") doesn't validate anything. This section could mislead users into adding unnecessary resource scaling under the impression it enables validation.

Consider either removing this section or accurately describing it as "configuring pipeline resources."

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@src/content/docs/fr/docs/live-updates/integrations/bitbucket-pipeline.mdx`
around lines 468 - 489, The "Pipeline Validation" section is misleading because
options.docker and size are runner/resource settings (options.docker, size: 2x)
and the example step named "Validate Pipeline" only echoes text (script: echo
"Pipeline validation successful") without performing any validation; either
remove this section or rename it to "Configuring pipeline resources" and update
the explanatory text to describe that options.docker and size control Docker
layer caching and runner resources, and if you want an actual validation example
replace the placeholder step (name: Validate Pipeline / script) with a real
validation command or reference to Bitbucket's pipeline linting/validation tool.

src/content/docs/fr/docs/live-updates/integrations/bitbucket-pipeline.mdx-102-102 (1)

102-102: ⚠️ Potential issue | 🟡 Minor

Invalid URL paths — same broken-link pattern as other integration files.

Apply the same corrections as azure-devops.mdx and gitlab-ci.mdx:

Broken	Correct
/docs/live-Mises à jour/Chiffrement/	/docs/live-updates/encryption/
/docs/live-Mises à jour/Chiffrement/#setting-up-Chiffrement	/docs/live-updates/encryption/#setting-up-encryption
/docs/live-Mises à jour/Canaux/	/docs/live-updates/channels/
/docs/live-Mises à jour/custom-storage/	/docs/live-updates/custom-storage/
/docs/live-Mises à jour/Mise à jour-behavior/	/docs/live-updates/update-behavior/

Also applies to: 104-104, 133-133, 493-496

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@src/content/docs/fr/docs/live-updates/integrations/bitbucket-pipeline.mdx` at
line 102, Replace the broken French-to-English mixed URL paths in
src/content/docs/fr/docs/live-updates/integrations/bitbucket-pipeline.mdx by
updating all occurrences of the listed broken paths to the correct English paths
(replace "/docs/live-Mises à jour/Chiffrement/" →
"/docs/live-updates/encryption/", "/docs/live-Mises à
jour/Chiffrement/#setting-up-Chiffrement" →
"/docs/live-updates/encryption/#setting-up-encryption", "/docs/live-Mises à
jour/Canaux/" → "/docs/live-updates/channels/", "/docs/live-Mises à
jour/custom-storage/" → "/docs/live-updates/custom-storage/", and
"/docs/live-Mises à jour/Mise à jour-behavior/" →
"/docs/live-updates/update-behavior/"); apply these replacements at the
instances mentioned in the review (including the link on the line containing
"Capgo's Chiffrement Fonctionnalité" and the additional occurrences around the
review-specified locations) so all internal links in the file point to the
correct /docs/live-updates/* targets.

src/content/docs/fr/docs/live-updates/integrations/gitlab-ci.mdx-117-117 (1)

117-117: ⚠️ Potential issue | 🟡 Minor

Invalid URL paths — same broken-link pattern as azure-devops.mdx.

All live-Mises à jour path segments are invalid. Apply the same corrections:

Broken	Correct
/docs/live-Mises à jour/Chiffrement/	/docs/live-updates/encryption/
/docs/live-Mises à jour/Chiffrement/#setting-up-Chiffrement	/docs/live-updates/encryption/#setting-up-encryption
/docs/live-Mises à jour/Canaux/	/docs/live-updates/channels/
/docs/live-Mises à jour/custom-storage/	/docs/live-updates/custom-storage/
/docs/live-Mises à jour/Mise à jour-behavior/	/docs/live-updates/update-behavior/

Also applies to: 119-119, 147-147, 421-424

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@src/content/docs/fr/docs/live-updates/integrations/gitlab-ci.mdx` at line
117, Replace all occurrences of the broken URL path segments that use
"live-Mises à jour" in
src/content/docs/fr/docs/live-updates/integrations/gitlab-ci.mdx with the
corrected English paths; specifically swap "/docs/live-Mises à
jour/Chiffrement/" -> "/docs/live-updates/encryption/", "/docs/live-Mises à
jour/Chiffrement/#setting-up-Chiffrement" ->
"/docs/live-updates/encryption/#setting-up-encryption", "/docs/live-Mises à
jour/Canaux/" -> "/docs/live-updates/channels/", "/docs/live-Mises à
jour/custom-storage/" -> "/docs/live-updates/custom-storage/", and
"/docs/live-Mises à jour/Mise à jour-behavior/" ->
"/docs/live-updates/update-behavior/"; update the occurrences noted at lines
around 117, 119, 147, and the block at 421-424 accordingly so all links in
gitlab-ci.mdx point to the corrected paths.

src/content/docs/fr/docs/live-updates/integrations/index.mdx-73-73 (1)

73-73: ⚠️ Potential issue | 🟡 Minor

Typo in API keys URL — console.capgo.Application should be console.capgo.app.

The URL on Line 73 uses console.capgo.Application/apikeys instead of console.capgo.app/apikeys (the correct domain used in all three sibling integration files). This link would be dead for users trying to retrieve their API token.

🐛 Proposed fix

-- A Capgo API token from [console.capgo.Application/apikeys](https://console.capgo.Application/apikeys)
+- A Capgo API token from [console.capgo.app/apikeys](https://console.capgo.app/apikeys)

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@src/content/docs/fr/docs/live-updates/integrations/index.mdx` at line 73,
Replace the incorrect domain in the Capgo API token link: find the string
"console.capgo.Application/apikeys" in the document (the Capgo API token bullet)
and change it to "console.capgo.app/apikeys" so the URL matches the other
integration files and points to the live site.

🧹 Nitpick comments (1)

src/content/docs/fr/docs/live-updates/integrations/azure-devops.mdx (1)

11-11: Content is mixed Franglais rather than French throughout.

Section headings and body text mix French nouns into English sentences — e.g., "Déployer Fonctionnalité branches to Test Canaux", "Terminé Configuration with multiple environments", "Suivant Steps", "Ajouter Microsoft Teams notifications". This pattern appears in all four new integration files.

This was likely produced by Cursor's partial translation. Depending on the project's documentation strategy, these pages should either be fully translated into French or use consistent English. The current mixed state harms readability for French-speaking users.

Also applies to: 87-89, 134-134, 164-168, 467-467, 577-577

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@src/content/docs/fr/docs/live-updates/integrations/azure-devops.mdx` at line
11, The document mixes French and English (Franglais) across headings and body —
e.g., phrases like "Mises à jour en direct", "Déployer Fonctionnalité branches
to Test Canaux", "Terminé Configuration", and "Suivant Steps" — so pick a single
language for the file (either fully French or fully English) and make the
translation consistent throughout; update all headings and body text in
src/content/docs/fr/docs/live-updates/integrations/azure-devops.mdx (and the
other flagged locations: lines referenced 87-89, 134, 164-168, 467, 577) to use
the chosen language, replacing mixed terms (Déployer, Fonctionnalité, Pousser,
Test, Déploiement, Ajouter Microsoft Teams notifications, etc.) with proper
translated equivalents, and run a pass to ensure terminology and tone match the
rest of the French docs.

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@src/content/docs/fr/docs/faq.mdx`:
- Around line 9-67: Replace every occurrence of the incorrect domain literal
"capgo.Application" with the canonical "capgo.app" and normalize internal doc
paths to lowercase slugs (e.g., change "/docs/FAQ/" and any links like
"https://capgo.Application/docs/FAQ/#..." to use "/docs/faq/" and
"https://capgo.app/docs/faq/..."); sweep the file for other mixed-case slugs
(examples in this diff: links containing "/docs/FAQ/", "/pricing/", "/privacy",
blog and CI guide URLs) and update them to their lowercase equivalents while
preserving the rest of each URL.

In `@src/content/docs/fr/docs/index.mdx`:
- Around line 10-16: Replace the non-canonical/case-mismatched route slugs in
this file: find and replace "/docs/getting-started/Démarrage rapide/" with
"/docs/getting-started/quickstart/", replace "/docs/FAQ/" with "/docs/faq/", and
replace "/Entreprise/" with "/enterprise/" so links use the canonical,
lowercased route slugs (check occurrences referenced by the link strings in this
file).

In `@src/content/docs/fr/docs/live-updates/breaking-changes.md`:
- Around line 1-203: The document has English body text mixed with French terms
while frontmatter sets locale: fr and title: "Breaking Changes"; translate the
entire body into fluent French (including headings, explanatory paragraphs,
notes like :::Conseil / :::Remarque / :::Avertissement, and inline text in
examples) keeping CLI commands, code blocks, and frontmatter unchanged, and
ensure terminology is consistent (e.g., replace "Application", "Canal", "Mises à
jour" uniformly) so the page served under the French locale is fully French and
coherent.
- Around line 34-40: Replace the invalid Starlight callout blocks by converting
each localized label to the recognized types: change every occurrence of
":::Conseil" to ":::tip[Conseil]", every ":::Remarque" to ":::note[Remarque]"
and every ":::Avertissement" to ":::caution[Avertissement]" so Starlight's
remarkAsides will render styled callouts; search for the literal strings
":::Conseil", ":::Remarque", and ":::Avertissement" in the document and update
both the opening and closing callout markers accordingly.

In `@src/content/docs/fr/docs/live-updates/channels.mdx`:
- Line 11: The French docs contain broken internal links: replace the
absolute/invalid paths and anchors in
src/content/docs/fr/docs/live-updates/channels.mdx — specifically the link
targets "/docs/getting-started/Démarrage rapide/",
"/docs/getting-started/Déployer/", "/docs/CLI/Commandes/#Désactiver-Mises à
jour-strategy" and "/blog/how-to-segment-Utilisateurs-by-plan-and-Canaux/" —
with correct relative paths that exist in the French site tree and normalize
them by removing accents and spaces and using lowercase hyphenated anchors
(e.g., use ".../demarrage-rapide/" or a relative
"../getting-started/demarrage-rapide.mdx" equivalent, ".../deployer/" ->
"deployer", change anchor "#désactiver-mises-à-jour-strategy" to
"#desactiver-mises-a-jour-strategy" or "#desactiver-mises-a-jour-strategie"
depending on target slug, and "/blog/..." to
"/blog/how-to-segment-users-by-plan-and-channels/" or the correct French slug);
update each link reference in the file (search for the exact link strings) so
they point to existing French doc pages and use URL-safe, lowercase hyphenated
anchors.

In `@src/content/docs/fr/docs/live-updates/china-configuration.mdx`:
- Around line 1-208: The page "Using Capgo in China" mixes English and French;
update the document content to be fully French by translating all English
strings (headings, instructional steps, sentences, code comments, Asides and
Steps text) into French while keeping technical identifiers intact (e.g.,
CapacitorConfig, capacitor.config.ts, CapacitorUpdater, updateUrl, statsUrl,
channelUrl, Aside, Steps); ensure code blocks remain unchanged except for
comments and surrounding prose, and remove mixed-language tokens like "Using
Capgo in China", "My App", "Test Appareil", "Terminé Exemple", "Performance
Considerations" etc., replacing them with correct French equivalents so the
entire page under the /fr route is consistently French.
- Line 188: Replace the incorrect domain suffix ".Application" in the two links
so they resolve correctly: change the email string "Support@capgo.Application"
to "Support@capgo.app" and the Discord URL "https://discord.capgo.Application"
to "https://discord.capgo.app" (these appear in the sentence referring to
multi-region Déploiement strategies and the Discord Communauté); ensure the
markdown link targets use the corrected values and keep the visible French text
unchanged.
- Line 143: Update the broken internal link in the Markdown content: replace the
invalid URL "/docs/live-Mises à jour/Mise à jour-behavior/" with the correct
English path "/docs/live-updates/update-behavior/" in
src/content/docs/fr/docs/live-updates/china-configuration.mdx so the anchor
points to the existing "update-behavior" page; keep the visible link text the
same or translate as appropriate but ensure the href uses the ASCII English
path.
- Around line 206-208: The three Next Steps links contain French words in their
URL paths ("/docs/live-Mises à jour/Mise à jour-behavior/", "/docs/live-Mises à
jour/Canaux/", "/docs/live-Mises à jour/Chiffrement/") which will 404; update
those hrefs in src/content/docs/fr/docs/live-updates/china-configuration.mdx to
the correct English/normalized paths (e.g.
"/docs/live-updates/update-behavior/", "/docs/live-updates/channels/",
"/docs/live-updates/encryption/") so the links point to the existing pages and
not the localized, invalid path fragments.

In `@src/content/docs/fr/docs/live-updates/compliance.mdx`:
- Around line 88-98: The SOC 2 Certification bullet contains a broken link and
there's a typo in the AI-Powered Code Review bullet: replace the URL
"trust.capgo.Application" with "trust.capgo.app" in the "**SOC 2
Certification**" line so the trust portal opens correctly, and change "Tirer
request" to "Pull request" in the "**AI-Powered Code Review**" bullet to fix the
typo; verify both edits in the lines containing "**SOC 2 Certification**" and
"**AI-Powered Code Review**" to ensure the link and text are updated.

In `@src/content/docs/fr/docs/live-updates/differentials.mdx`:
- Around line 1-81: The page mixes English and French — translate all remaining
English content into natural French while keeping technical tokens and UI
artifacts intact: convert prose like "Capgo's Live Mise à jour system",
paragraphs under "How Differential Mises à jour Work", "Enabling/Enforcing
Differential Mises à jour", troubleshooting bullets, Step list items, image alt
text "Bundle type", and the final explanatory paragraphs into French; preserve
CLI flags and code blocks (`--partial`, `--partial-only`, `npx `@capgo/cli`@latest
bundle upload --partial-only`) and keep imported components (Aside, Steps) and
manifest/manifest-related terms consistent, then proofread for consistent
capitalization of terms like Appareil, Application, Télécharger, Vérifier,
Journaux so the document is fully French and coherent.

In `@src/content/docs/fr/docs/live-updates/encryption.mdx`:
- Around line 1-344: The page at encryption.mdx is written mostly in English
with scattered French words (e.g., "Chiffrement", "Appareil", "Développement"),
causing language mismatch for locale: fr; translate the entire document body
(headings, paragraphs, captions, step descriptions, warnings, code comments and
UI text inside <Aside> and <Steps> blocks) into fluent French so the content is
fully French, keep existing structure and component usage (Aside, Steps,
headings like "Aperçu", "Comment fonctionne le chiffrement", "Méthodes de
chiffrement", "Paramètres", "Dépannage"), and ensure any CLI examples, option
names and file names remain accurate and unchanged where they must be (e.g., npx
`@capgo/cli` commands, .capgo_key_v2 filenames) while converting surrounding
explanatory text to French.
- Around line 342-344: Update the two broken internal links in the "Next Steps"
list in src/content/docs/fr/docs/live-updates/encryption.mdx: replace the French
path segments "/docs/live-Mises à jour/custom-storage/" and "/docs/live-Mises à
jour/Canaux/" with the correct English URL paths
"/docs/live-updates/custom-storage/" and "/docs/live-updates/channels/"
respectively (preserve the visible link text "Custom Storage" and
"Canaux"/"Channels" as appropriate), and verify the third CI/CD link remains
unchanged.
- Line 96: The internal link in the French page uses a French slug "/docs/Mise à
niveau/Chiffrement-v1-to-v2/" which causes a 404; update the href to the English
slug for the upgrade docs (e.g. "/docs/upgrade/Chiffrement-v1-to-v2/" or the
exact English path your site uses) wherever the string appears in
src/content/docs/fr/docs/live-updates/encryption.mdx so the link resolves
correctly; ensure you replace only the path portion and keep surrounding
text/markdown intact.

In `@src/content/docs/fr/docs/live-updates/integrations/index.mdx`:
- Around line 17-38: The LinkCard components use hardcoded absolute hrefs (e.g.,
in the LinkCard entries for "Azure DevOps", "GitLab CI/CD", "GitHub Actions",
"Bitbucket Pipelines") which will always point to the default locale; update
those href props to be locale-aware by either prefixing each path with "/fr/"
for this French page (e.g., "/fr/docs/live-updates/integrations/azure-devops/")
or by generating the URL with the Astro/i18n helper (e.g., use
getRelativeLocaleUrl(...) when building the href passed into each LinkCard) so
links resolve to the correct locale at runtime.

In `@src/content/docs/fr/docs/live-updates/rollbacks.mdx`:
- Around line 1-162: The document has French frontmatter (locale: fr, title:
Restaurations) but the body is mostly English with scattered French tokens;
replace the entire article body with a proper French translation so the content
matches locale: fr, preserving technical identifiers and code samples (e.g.,
notifyAppReady(), CapacitorUpdater) unchanged; translate UI labels, Steps items,
Asides, image alt text (e.g., "Restauration UI interface", "Canal management
Options") and all prose into fluent French, remove AI-artifact mixed-language
phrases (e.g., "Retour", "Construction", "Appareils") by using correct French
equivalents consistently, and keep the structure and examples intact.

In `@src/content/docs/fr/docs/live-updates/update-behavior.mdx`:
- Around line 1-216: The page is marked locale: fr but the body is mostly
English; translate the entire document content into French, keeping the
frontmatter locale: fr and the existing headings (e.g., "Mise à jour Behavior",
"Default Mise à jour Flow") and components (<Steps>, <Aside>) intact; ensure all
UI terms and examples (like `setMultiDelay`, `directUpdate`, `autoSplashscreen`,
`keepUrlPathAfterReload`, code blocks, and links) are presented in French and
fix consistent terminology (use "Mise à jour"/"Mises à jour" uniformly), and
update any in-text links or captions (e.g., Delta Updates / differentials) to
their French equivalents so the /fr page is fully French.
- Line 112: The internal link in
src/content/docs/fr/docs/live-updates/update-behavior.mdx points to an invalid
path with French characters and spaces; update the href in the "Learn more in
the [Delta Mises à jour Documentation](...)" link to the correct canonical path
/fr/docs/live-updates/differentials/ (keep the visible link text as-is if
desired) so the link resolves to fr/docs/live-updates/differentials.mdx.

---

Outside diff comments:
In `@src/content/docs/fr/live-updates/features.mdx`:
- Line 299: Fix the typo in the sentence containing "Vérifiez l.integrité du
bundle avec des signatures cryptographiques pour prévenir toute altération." by
replacing the period with an apostrophe so it reads "Vérifiez l'intégrité du
bundle..." — update the string in the same content block (the sentence starting
with "Vérifiez l.integrité") to use the correct character.
- Line 325: The sentence and the location marker are run together; update the
document content where the string "Exiger que tous les bundles soient chiffrés
au niveau de l'organisation.**Emplacement :** Web Dashboard → Organization →
Security" appears so there is a space or a line break before "**Emplacement :**"
(e.g., "...l'organisation. **Emplacement :** ..." or place "**Emplacement :**
Web Dashboard..." on the next line) to separate the sentence from the location
marker.

---

Minor comments:
In `@src/content/docs/fr/docs/live-updates/differentials.mdx`:
- Around line 35-38: Add the missing example command for the "Enabling
Differential Mises à jour" section by inserting a fenced code block showing how
to upload a new version with the --partial flag; specifically add a shell code
block containing the suggested command (e.g., npx `@capgo/cli`@latest bundle
upload --partial) immediately after the sentence that mentions `--partial` so
the heading "Enabling Differential Mises à jour" includes an executable example
before the next section "Enforcing Differential Mises à jour".

In `@src/content/docs/fr/docs/live-updates/encryption.mdx`:
- Line 323: Replace the British spelling in the SOC 2 label so it matches
American English used elsewhere: update the string "SOC 2 (Service Organisation
Control 2)" to "SOC 2 (Service Organization Control 2)" in the document (search
for the exact phrase "SOC 2 (Service Organisation Control 2)").

In `@src/content/docs/fr/docs/live-updates/integrations/azure-devops.mdx`:
- Line 136: Replace the invalid French URL path segments that contain spaces
with the correct English route segments in this file (and similarly in
gitlab-ci.mdx, bitbucket-pipeline.mdx, and index.mdx): update occurrences of
"/docs/live-Mises à jour/Chiffrement/" -> "/docs/live-updates/encryption/",
"/docs/live-Mises à jour/Chiffrement/#setting-up-Chiffrement" ->
"/docs/live-updates/encryption/#setting-up-encryption", "/docs/live-Mises à
jour/Canaux/" -> "/docs/live-updates/channels/", "/docs/live-Mises à
jour/custom-storage/" -> "/docs/live-updates/custom-storage/", and
"/docs/live-Mises à jour/Mise à jour-behavior/" ->
"/docs/live-updates/update-behavior/"; search for the exact broken strings in
azure-devops.mdx (lines near the shown instances) and replace them so links
point to the existing /docs/live-updates/* routes.

In `@src/content/docs/fr/docs/live-updates/integrations/bitbucket-pipeline.mdx`:
- Around line 468-489: The "Pipeline Validation" section is misleading because
options.docker and size are runner/resource settings (options.docker, size: 2x)
and the example step named "Validate Pipeline" only echoes text (script: echo
"Pipeline validation successful") without performing any validation; either
remove this section or rename it to "Configuring pipeline resources" and update
the explanatory text to describe that options.docker and size control Docker
layer caching and runner resources, and if you want an actual validation example
replace the placeholder step (name: Validate Pipeline / script) with a real
validation command or reference to Bitbucket's pipeline linting/validation tool.
- Line 102: Replace the broken French-to-English mixed URL paths in
src/content/docs/fr/docs/live-updates/integrations/bitbucket-pipeline.mdx by
updating all occurrences of the listed broken paths to the correct English paths
(replace "/docs/live-Mises à jour/Chiffrement/" →
"/docs/live-updates/encryption/", "/docs/live-Mises à
jour/Chiffrement/#setting-up-Chiffrement" →
"/docs/live-updates/encryption/#setting-up-encryption", "/docs/live-Mises à
jour/Canaux/" → "/docs/live-updates/channels/", "/docs/live-Mises à
jour/custom-storage/" → "/docs/live-updates/custom-storage/", and
"/docs/live-Mises à jour/Mise à jour-behavior/" →
"/docs/live-updates/update-behavior/"); apply these replacements at the
instances mentioned in the review (including the link on the line containing
"Capgo's Chiffrement Fonctionnalité" and the additional occurrences around the
review-specified locations) so all internal links in the file point to the
correct /docs/live-updates/* targets.

In `@src/content/docs/fr/docs/live-updates/integrations/github-actions.mdx`:
- Around line 62-85: The "Deploy to Capgo" GitHub Actions step has incorrect
YAML indentation for the run and env keys in the step titled "Deploy to Capgo";
fix it by aligning the run: and env: keys at the same indentation level as name:
and uses:, ensure the shell block under run has its commands indented one level
deeper, and place CAPGO_TOKEN under env as a mapping (CAPGO_TOKEN: ${{
secrets.CAPGO_TOKEN }}); verify there are no extra leading spaces before run and
that the comment about --key-data-v2 remains properly indented under env or the
run block as appropriate.

In `@src/content/docs/fr/docs/live-updates/integrations/gitlab-ci.mdx`:
- Line 117: Replace all occurrences of the broken URL path segments that use
"live-Mises à jour" in
src/content/docs/fr/docs/live-updates/integrations/gitlab-ci.mdx with the
corrected English paths; specifically swap "/docs/live-Mises à
jour/Chiffrement/" -> "/docs/live-updates/encryption/", "/docs/live-Mises à
jour/Chiffrement/#setting-up-Chiffrement" ->
"/docs/live-updates/encryption/#setting-up-encryption", "/docs/live-Mises à
jour/Canaux/" -> "/docs/live-updates/channels/", "/docs/live-Mises à
jour/custom-storage/" -> "/docs/live-updates/custom-storage/", and
"/docs/live-Mises à jour/Mise à jour-behavior/" ->
"/docs/live-updates/update-behavior/"; update the occurrences noted at lines
around 117, 119, 147, and the block at 421-424 accordingly so all links in
gitlab-ci.mdx point to the corrected paths.

In `@src/content/docs/fr/docs/live-updates/integrations/index.mdx`:
- Around line 78-80: The Related Documentation links use incorrect localized
paths; update the hrefs for the link texts [Canaux], [Chiffrement], and [Mise à
jour Behavior] so they point to the correct English-slugged routes: replace
'/docs/live-Mises à jour/Canaux/' with '/docs/live-updates/channels/',
'/docs/live-Mises à jour/Chiffrement/' with '/docs/live-updates/encryption/',
and '/docs/live-Mises à jour/Mise à jour-behavior/' with
'/docs/live-updates/update-behavior/' in the index.mdx content.
- Line 73: Replace the incorrect domain in the Capgo API token link: find the
string "console.capgo.Application/apikeys" in the document (the Capgo API token
bullet) and change it to "console.capgo.app/apikeys" so the URL matches the
other integration files and points to the live site.

In `@src/content/docs/fr/docs/live-updates/rollbacks.mdx`:
- Line 74: The phrase "Journal in to the [Capgo Tableau de bord]" is incorrect
English; replace that exact string with the correct English text "Log in to the
[Capgo Dashboard]" (or if the file is intended to be French, use "Connectez-vous
au [Tableau de bord Capgo]") by updating the content in
src/content/docs/fr/docs/live-updates/rollbacks.mdx where the text "Journal in
to the [Capgo Tableau de bord]" appears.

---

Duplicate comments:
In `@src/content/docs/fr/docs/getting-help.mdx`:
- Line 11: The markdown link uses a mis-cased domain
("https://discord.capgo.Application") causing inconsistent normalization; update
the URL to the correctly cased canonical domain (e.g., replace
"https://discord.capgo.Application" with "https://discord.capgo.application" or
the canonical domain used elsewhere) and make the same change for the duplicate
occurrence of that URL in the file so all links match.

In `@src/content/docs/fr/docs/live-updates/china-configuration.mdx`:
- Line 198: Replace the broken links in the troubleshooting sentence by updating
the visible and target link texts: change "Support@capgo.Application" to the
correct support email (e.g., "Support@capgo.app") and change
"https://discord.capgo.Application" (and the visible
"discord.capgo.Application") to the correct Discord invite URL (e.g.,
"https://discord.capgo.app"); update the mailto: and href values accordingly so
both the display text and link targets match the corrected domains.

In `@src/content/docs/fr/docs/live-updates/custom-storage.mdx`:
- Around line 300-302: The three internal links in the "Suivant Steps" list
(link texts "Canaux", "Mise à jour Behavior", "CI/CD Integration") use paths
with spaces/accents and will 404; update their hrefs to the normalized slugs
used across the FR docs—e.g. replace "/docs/live-Mises à jour/Canaux/" and
"/docs/live-Mises à jour/Mise à jour-behavior/" with the normalized live-updates
slugs (e.g. "/docs/live-updates/channels/" and
"/docs/live-updates/update-behavior/") and ensure
"/docs/getting-started/cicd-integration/" uses the exact existing slug for CI/CD
integration so all three internal links match the canonical FR doc slugs.

---

Nitpick comments:
In `@src/content/docs/fr/docs/live-updates/integrations/azure-devops.mdx`:
- Line 11: The document mixes French and English (Franglais) across headings and
body — e.g., phrases like "Mises à jour en direct", "Déployer Fonctionnalité
branches to Test Canaux", "Terminé Configuration", and "Suivant Steps" — so pick
a single language for the file (either fully French or fully English) and make
the translation consistent throughout; update all headings and body text in
src/content/docs/fr/docs/live-updates/integrations/azure-devops.mdx (and the
other flagged locations: lines referenced 87-89, 134, 164-168, 467, 577) to use
the chosen language, replacing mixed terms (Déployer, Fonctionnalité, Pousser,
Test, Déploiement, Ajouter Microsoft Teams notifications, etc.) with proper
translated equivalents, and run a pass to ensure terminology and tone match the
rest of the French docs.

---

ℹ️ Review info

Configuration used: defaults

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 971be10 and f313373.

📒 Files selected for processing (20)

• src/content/docs/fr/docs/faq.mdx
• src/content/docs/fr/docs/getting-help.mdx
• src/content/docs/fr/docs/how-to.mdx
• src/content/docs/fr/docs/index.mdx
• src/content/docs/fr/docs/live-updates/breaking-changes.md
• src/content/docs/fr/docs/live-updates/channels.mdx
• src/content/docs/fr/docs/live-updates/china-configuration.mdx
• src/content/docs/fr/docs/live-updates/compliance.mdx
• src/content/docs/fr/docs/live-updates/custom-storage.mdx
• src/content/docs/fr/docs/live-updates/differentials.mdx
• src/content/docs/fr/docs/live-updates/encryption.mdx
• src/content/docs/fr/docs/live-updates/integrations/azure-devops.mdx
• src/content/docs/fr/docs/live-updates/integrations/bitbucket-pipeline.mdx
• src/content/docs/fr/docs/live-updates/integrations/github-actions.mdx
• src/content/docs/fr/docs/live-updates/integrations/gitlab-ci.mdx
• src/content/docs/fr/docs/live-updates/integrations/index.mdx
• src/content/docs/fr/docs/live-updates/rollbacks.mdx
• src/content/docs/fr/docs/live-updates/update-behavior.mdx
• src/content/docs/fr/live-updates/features.mdx
• src/content/docs/fr/live-updates/update-types.mdx

[coderabbitai]

⚠️ Potential issue | 🟠 Major

🧩 Analysis chain

🏁 Script executed:

# Search for domain patterns across the entire codebase
rg "capgo\.(app|Application)" --no-heading -c | head -20

Repository: Cap-go/website

Length of output: 665

---

🏁 Script executed:

# Check what domains are used in the English docs for comparison
fd -e "mdx" -e "md" . src/content/docs/en | head -5 | xargs rg "capgo\.(app|Application)" -n | head -20

Repository: Cap-go/website

Length of output: 2479

---

🏁 Script executed:

# Look for the actual file to examine its links
cat -n src/content/docs/fr/docs/faq.mdx | head -70

Repository: Cap-go/website

Length of output: 6636

---

🏁 Script executed:

# Check if there are any configuration or constants that define the canonical domain
rg "capgo\.(app|Application)" -A2 -B2 src/ | head -40

Repository: Cap-go/website

Length of output: 2403

---

🏁 Script executed:

# Search for path patterns in French docs
rg "docs/[a-zA-Z]" src/content/docs/fr --no-heading | head -20

Repository: Cap-go/website

Length of output: 2921

---

Replace all instances of capgo.Application with capgo.app and normalize internal paths to lowercase.

This file contains broken domain references (capgo.Application instead of capgo.app) and inconsistent path casing (e.g., /docs/FAQ/ instead of /docs/faq/). The canonical domain across the codebase is capgo.app, and internal documentation paths consistently use lowercase slugs. Replace all occurrences in this file and sweep across the other affected line ranges (117-121, 161-170, 222-233, 317-333).

🧰 Tools

🪛 LanguageTool

[grammar] ~15-~15: Ensure spelling is correct
Context: ...e Capacitor works. "Code Pousser" is a Référence to the name of a Déployer Fonctionnalit...

(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)

---

[grammar] ~19-~19: Ensure spelling is correct
Context: ...le and a Libération?") We use the term "Libération" to mean preparing a binary for the Appl...

(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)

---

[style] ~19-~19: Consider a more concise word here.
Context: ...ng a binary for the Application stores. In order to later generate a Bundle Capgo needs to ...

(IN_ORDER_TO_PREMIUM)

---

[uncategorized] ~27-~27: The official name of this software platform is spelled with a capital “H”.
Context: ... À propos our roadmap or priorities via Github issues or [Discord](https://discord.cap...

(GITHUB)

---

[uncategorized] ~47-~47: The official name of this software platform is spelled with a capital “H”.
Context: ...e've published a Guide for [Android and Github Actions](https://capgo.Application/blog...

(GITHUB)

---

[grammar] ~61-~61: Ensure spelling is correct
Context: ....4 Simulator?") No. Due to an upstream Problème affecting the iOS 18.4 Simulator, Capgo...

(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@src/content/docs/fr/docs/faq.mdx` around lines 9 - 67, Replace every
occurrence of the incorrect domain literal "capgo.Application" with the
canonical "capgo.app" and normalize internal doc paths to lowercase slugs (e.g.,
change "/docs/FAQ/" and any links like "https://capgo.Application/docs/FAQ/#..."
to use "/docs/faq/" and "https://capgo.app/docs/faq/..."); sweep the file for
other mixed-case slugs (examples in this diff: links containing "/docs/FAQ/",
"/pricing/", "/privacy", blog and CI guide URLs) and update them to their
lowercase equivalents while preserving the rest of each URL.

[coderabbitai]

⚠️ Potential issue | 🟠 Major

🧩 Analysis chain

🏁 Script executed:

cat -n src/content/docs/fr/docs/index.mdx

Repository: Cap-go/website

Length of output: 3618

---

🏁 Script executed:

# Find documentation files related to quickstart, FAQ, Enterprise
fd -t f "quickstart|démarrage|faq|entreprise" --ignore-case src/content/docs/

Repository: Cap-go/website

Length of output: 875

---

🏁 Script executed:

# List the docs directory structure to understand the slug organization
find src/content/docs -type d -name "*getting-started*" -o -type d -name "*FAQ*" -o -type d -name "*Entreprise*" | head -20

Repository: Cap-go/website

Length of output: 418

---

🏁 Script executed:

# Search for enterprise/Entreprise files and paths
fd -t f "enterprise|entreprise" --ignore-case src/content/ | grep -E "\.(mdx|md|astro)$"

Repository: Cap-go/website

Length of output: 40

---

🏁 Script executed:

# Check if there's a dedicated enterprise page or if it's just a link
find src/content -type f -name "*enterprise*" -o -type f -name "*Entreprise*"

Repository: Cap-go/website

Length of output: 40

---

🏁 Script executed:

# Look at the actual route structure by examining Astro config or similar
find . -maxdepth 2 -name "astro.config*" -o -name "tsconfig*" | head -5

Repository: Cap-go/website

Length of output: 92

---

🏁 Script executed:

# Check Astro config for route structure
head -50 astro.config.mjs

Repository: Cap-go/website

Length of output: 2177

---

🏁 Script executed:

# Check if there are locale-specific route mappings or redirects
rg "Démarrage|démarrage|quickstart" src/content/docs/fr/docs/index.mdx -B 2 -A 2

Repository: Cap-go/website

Length of output: 1049

---

🏁 Script executed:

# Look for any config files that might define route mappings or i18n
find src -name "*.ts" -o -name "*.js" | xargs grep -l "Démarrage\|quickstart\|faq\|FAQ" | head -10

Repository: Cap-go/website

Length of output: 75

---

🏁 Script executed:

# Verify the exact slug/path structure for French docs
ls -la src/content/docs/fr/docs/getting-started/ 2>/dev/null || ls -la src/content/docs/fr/getting-started/

Repository: Cap-go/website

Length of output: 643

---

🏁 Script executed:

# Check if faq.mdx exists and what the actual route would be
ls -la src/content/docs/fr/docs/faq.mdx src/content/docs/fr/faq.mdx 2>/dev/null || echo "Checking alternate paths..."
rg "slug:|route:" src/content/docs/fr/docs/faq.mdx src/content/docs/fr/faq.mdx 2>/dev/null

Repository: Cap-go/website

Length of output: 218

---

🏁 Script executed:

# Search for any enterprise page or routing
rg "enterprise|Entreprise" src/content --type mdx --type ts --type js | head -20

Repository: Cap-go/website

Length of output: 85

---

🏁 Script executed:

# Check if there are any starlight route mappings or slug definitions
rg "slug:|id:|" src/content/docs/fr/getting-started/quickstart.mdx src/content/docs/fr/docs/faq.mdx src/content/docs/fr/faq.mdx | head -20

Repository: Cap-go/website

Length of output: 2020

---

🏁 Script executed:

# Check the starlight configuration for route settings
rg "sidebar|routes|locales" astro.config.mjs | head -20

Repository: Cap-go/website

Length of output: 307

---

🏁 Script executed:

# See if there's a /enterprise/ page anywhere
find src -type f \( -name "*.mdx" -o -name "*.astro" \) | xargs grep -l "/enterprise" | head -10

Repository: Cap-go/website

Length of output: 408

---

🏁 Script executed:

# Look at src/pages to understand the route structure
ls -la src/pages/ 2>/dev/null | head -20

Repository: Cap-go/website

Length of output: 1264

---

🏁 Script executed:

# Verify the actual routes by checking how Starlight handles slugs
head -20 src/content/docs/fr/getting-started/quickstart.mdx

Repository: Cap-go/website

Length of output: 583

---

🏁 Script executed:

# Check if there are any custom slug definitions in the faq files
head -20 src/content/docs/fr/faq.mdx

Repository: Cap-go/website

Length of output: 1460

---

🏁 Script executed:

# Verify the enterprise page route
head -20 src/pages/enterprise.astro

Repository: Cap-go/website

Length of output: 1045

---

Fix mixed slug formats: use /docs/getting-started/quickstart/, /docs/faq/, and /enterprise/.

The page uses non-canonical slugs for three key links. Lines 11, 35, and 66 reference /docs/getting-started/Démarrage rapide/ (French title instead of filename slug), line 68 uses /docs/FAQ/ (uppercase), and line 69 uses /Entreprise/ (capitalized French). These will 404 on case-sensitive servers. Use the actual route slugs: /docs/getting-started/quickstart/, /docs/faq/, and /enterprise/.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@src/content/docs/fr/docs/index.mdx` around lines 10 - 16, Replace the
non-canonical/case-mismatched route slugs in this file: find and replace
"/docs/getting-started/Démarrage rapide/" with
"/docs/getting-started/quickstart/", replace "/docs/FAQ/" with "/docs/faq/", and
replace "/Entreprise/" with "/enterprise/" so links use the canonical,
lowercased route slugs (check occurrences referenced by the link strings in this
file).

[coderabbitai]

⚠️ Potential issue | 🟠 Major

Content is not French — same English/French language mixing issue

Like the other new files in this PR, the body is English prose with French terms scattered throughout. The page is served to French users under /fr/docs/live-updates/breaking-changes/.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@src/content/docs/fr/docs/live-updates/breaking-changes.md` around lines 1 -
203, The document has English body text mixed with French terms while
frontmatter sets locale: fr and title: "Breaking Changes"; translate the entire
body into fluent French (including headings, explanatory paragraphs, notes like
:::Conseil / :::Remarque / :::Avertissement, and inline text in examples)
keeping CLI commands, code blocks, and frontmatter unchanged, and ensure
terminology is consistent (e.g., replace "Application", "Canal", "Mises à jour"
uniformly) so the page served under the French locale is fully French and
coherent.

[coderabbitai]

⚠️ Potential issue | 🟠 Major

🧩 Analysis chain

🏁 Script executed:

# Check if file exists and examine lines 34-40
if [ -f "src/content/docs/fr/docs/live-updates/breaking-changes.md" ]; then
  echo "=== File exists. Checking line count ==="
  wc -l src/content/docs/fr/docs/live-updates/breaking-changes.md
  echo ""
  echo "=== Lines 34-40 ==="
  sed -n '34,40p' src/content/docs/fr/docs/live-updates/breaking-changes.md
else
  echo "File not found"
fi

Repository: Cap-go/website

Length of output: 497

---

🏁 Script executed:

# Count all occurrences of each invalid callout type
echo "=== Counting callout blocks ==="
echo ":::Conseil blocks:"
rg ':::Conseil' src/content/docs/fr/docs/live-updates/breaking-changes.md | wc -l
echo ""
echo ":::Remarque blocks:"
rg ':::Remarque' src/content/docs/fr/docs/live-updates/breaking-changes.md | wc -l
echo ""
echo ":::Avertissement blocks:"
rg ':::Avertissement' src/content/docs/fr/docs/live-updates/breaking-changes.md | wc -l
echo ""
echo "=== Total invalid callout blocks ==="
rg ':::(Conseil|Remarque|Avertissement)' src/content/docs/fr/docs/live-updates/breaking-changes.md | wc -l

Repository: Cap-go/website

Length of output: 201

---

🏁 Script executed:

# List all callout blocks to see context
echo "=== All callout block instances ==="
rg -n ':::(Conseil|Remarque|Avertissement)' src/content/docs/fr/docs/live-updates/breaking-changes.md

Repository: Cap-go/website

Length of output: 225

---

🌐 Web query:

Starlight callout valid types remarkAsides note tip caution danger

💡 Result:

In Astro Starlight, the built-in callouts (a.k.a. asides/admonitions, implemented via the <Aside> component and the ::: Markdown syntax powered by Starlight’s aside support/“remark asides”) support these valid type values:

• note
• tip
• caution
• danger [1]

These are also the only allowed values for the <Aside type="..."> prop. [1]

Sources: [1]

---

Fix invalid Starlight callout syntax — eight callout blocks will not render with styling

Starlight's remarkAsides plugin only recognizes note, tip, caution, and danger as valid callout types. This file contains eight invalid callout blocks using :::Conseil, :::Remarque, and :::Avertissement (lines 34, 71, 88, 119, 167, 171, 175, 201), which will not render as styled callouts.

Use the correct syntax for French-titled callouts: :::tip[Conseil], :::note[Remarque], :::caution[Avertissement].

✏️ Proposed fix (all occurrences)

-:::Conseil
+:::tip[Conseil]

-:::Remarque
+:::note[Remarque]

-:::Avertissement
+:::caution[Avertissement]

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	:::Conseil
	**Benefits of this approach:**
	- **Always have control** over which Utilisateurs receive Mises à jour
	- **No dynamic Canal switching** needed in your Application code
	- **Clear separation** between different Application versions
	- **Flexibility** to Pousser Mises à jour to any specific Version group
	:::
	:::tip[Conseil]
	**Benefits of this approach:**
	- **Always have control** over which Utilisateurs receive Mises à jour
	- **No dynamic Canal switching** needed in your Application code
	- **Clear separation** between different Application versions
	- **Flexibility** to Pousser Mises à jour to any specific Version group
	:::

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@src/content/docs/fr/docs/live-updates/breaking-changes.md` around lines 34 -
40, Replace the invalid Starlight callout blocks by converting each localized
label to the recognized types: change every occurrence of ":::Conseil" to
":::tip[Conseil]", every ":::Remarque" to ":::note[Remarque]" and every
":::Avertissement" to ":::caution[Avertissement]" so Starlight's remarkAsides
will render styled callouts; search for the literal strings ":::Conseil",
":::Remarque", and ":::Avertissement" in the document and update both the
opening and closing callout markers accordingly.

[coderabbitai]

⚠️ Potential issue | 🟠 Major

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash

# First, explore the French docs directory structure
echo "=== FR Docs Directory Structure ==="
fd -e md -e mdx . src/content/docs/fr/docs 2>/dev/null | head -30

echo -e "\n=== All links in channels.mdx ==="
# Extract all links from the file
cat src/content/docs/fr/docs/live-updates/channels.mdx 2>/dev/null | grep -oE '\[([^\]]+)\]\(([^)]+)\)' | head -20

echo -e "\n=== Specific link URLs in channels.mdx ==="
# More targeted extraction
rg -o '\[([^\]]+)\]\(([^)]+)\)' -r '$2' src/content/docs/fr/docs/live-updates/channels.mdx 2>/dev/null | sort -u

echo -e "\n=== Check for referenced documents ==="
# Check if the getting-started docs exist
ls -la src/content/docs/fr/docs/getting-started/ 2>/dev/null || echo "getting-started dir not found"
ls -la src/content/docs/fr/docs/CLI/ 2>/dev/null || echo "CLI dir not found"

Repository: Cap-go/website

Length of output: 1450

---

🏁 Script executed:

#!/bin/bash

# Get file structure to understand slugs better
echo "=== File structure with index files ==="
find src/content/docs/fr/docs -type f \( -name "*.md" -o -name "*.mdx" \) | sort

echo -e "\n=== Check for Démarrage rapide files ==="
find src/content/docs/fr/docs -type f -iname "*démarrage*" -o -iname "*demarrage*"

echo -e "\n=== Check canonical slugs by examining frontmatter ==="
# Check a few files to see how they define slugs
fd -e mdx . src/content/docs/fr/docs/getting-started 2>/dev/null | head -5 | xargs cat 2>/dev/null | head -50

Repository: Cap-go/website

Length of output: 1179

---

🏁 Script executed:

#!/bin/bash

echo "=== English docs structure (getting-started) ==="
ls -la src/content/docs/en/docs/getting-started/ 2>/dev/null || echo "Not found in en/docs"
find src/content/docs/en/docs/getting-started -type f 2>/dev/null | sort

echo -e "\n=== Check root docs structure ==="
ls -la src/content/docs/getting-started/ 2>/dev/null || echo "Not found at root"
find src/content/docs/getting-started -type f 2>/dev/null | sort

echo -e "\n=== Full content of channels.mdx to see all links ==="
cat src/content/docs/fr/docs/live-updates/channels.mdx

Repository: Cap-go/website

Length of output: 15211

---

Fix broken internal links—directories don't exist in French docs structure.

Several internal links reference non-existent paths with problematic characters:

• /docs/getting-started/Démarrage rapide/ (line 11)
• /docs/getting-started/Déployer/ (line 187-198)
• /docs/CLI/Commandes/#Désactiver-Mises à jour-strategy (line 121-122)
• /blog/how-to-segment-Utilisateurs-by-plan-and-Canaux/ (line 288)

The getting-started and CLI directories don't exist in the French docs structure. Additionally, links with spaces and accents will fail URL resolution. Replace with working relative links or correct paths, and normalize anchors (remove spaces, use lowercase with hyphens).

🧰 Tools

🪛 LanguageTool

[grammar] ~11-~11: Ensure spelling is correct
Context: ...rrage rapide/) in your Application, any Natif binary configured to that Canal will Vé...

(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)

---

[grammar] ~11-~11: Ensure spelling is correct
Context: ...at any time and can also roll Retour to Précédent builds if needed. ## How a Appareil pi...

(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@src/content/docs/fr/docs/live-updates/channels.mdx` at line 11, The French
docs contain broken internal links: replace the absolute/invalid paths and
anchors in src/content/docs/fr/docs/live-updates/channels.mdx — specifically the
link targets "/docs/getting-started/Démarrage rapide/",
"/docs/getting-started/Déployer/", "/docs/CLI/Commandes/#Désactiver-Mises à
jour-strategy" and "/blog/how-to-segment-Utilisateurs-by-plan-and-Canaux/" —
with correct relative paths that exist in the French site tree and normalize
them by removing accents and spaces and using lowercase hyphenated anchors
(e.g., use ".../demarrage-rapide/" or a relative
"../getting-started/demarrage-rapide.mdx" equivalent, ".../deployer/" ->
"deployer", change anchor "#désactiver-mises-à-jour-strategy" to
"#desactiver-mises-a-jour-strategy" or "#desactiver-mises-a-jour-strategie"
depending on target slug, and "/blog/..." to
"/blog/how-to-segment-users-by-plan-and-channels/" or the correct French slug);
update each link reference in the file (search for the exact link strings) so
they point to existing French doc pages and use URL-safe, lowercase hyphenated
anchors.

[coderabbitai]

⚠️ Potential issue | 🔴 Critical

Two broken internal links in "Suivant Steps" — French words in URL paths will 404

/docs/live-Mises à jour/custom-storage/ and /docs/live-Mises à jour/Canaux/ embed French words in the URL path and will 404.

✏️ Proposed fix

-- Learn À propos [Custom Storage](/docs/live-Mises à jour/custom-storage/) to use Chiffrement with your own infrastructure
-- Explore [Canaux](/docs/live-Mises à jour/Canaux/) to manage Chiffré Bundles across environments
+- Learn about [Custom Storage](/fr/docs/live-updates/custom-storage/) to use encryption with your own infrastructure
+- Explore [Channels](/fr/docs/live-updates/channels/) to manage encrypted bundles across environments

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	- Learn À propos [Custom Storage](/docs/live-Mises à jour/custom-storage/) to use Chiffrement with your own infrastructure
	- Explore [Canaux](/docs/live-Mises à jour/Canaux/) to manage Chiffré Bundles across environments
	- Set up [CI/CD Integration](/docs/getting-started/cicd-integration/) to automate Chiffré deployments
	- Learn about [Custom Storage](/fr/docs/live-updates/custom-storage/) to use encryption with your own infrastructure
	- Explore [Channels](/fr/docs/live-updates/channels/) to manage encrypted bundles across environments
	- Set up [CI/CD Integration](/docs/getting-started/cicd-integration/) to automate Chiffré deployments

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@src/content/docs/fr/docs/live-updates/encryption.mdx` around lines 342 - 344,
Update the two broken internal links in the "Next Steps" list in
src/content/docs/fr/docs/live-updates/encryption.mdx: replace the French path
segments "/docs/live-Mises à jour/custom-storage/" and "/docs/live-Mises à
jour/Canaux/" with the correct English URL paths
"/docs/live-updates/custom-storage/" and "/docs/live-updates/channels/"
respectively (preserve the visible link text "Custom Storage" and
"Canaux"/"Channels" as appropriate), and verify the third CI/CD link remains
unchanged.

[coderabbitai]

⚠️ Potential issue | 🟠 Major

🧩 Analysis chain

🌐 Web query:

Astro Starlight absolute href links multilingual locale routing

💡 Result:

For Astro + Starlight multilingual sites, don’t hardcode href="/..." (it won’t automatically pick up the current locale, and Astro’s base also won’t “rewrite” your anchor hrefs for you). Instead, generate locale-aware URLs.

1) Use Astro’s i18n URL helpers (recommended)

Astro provides helpers that build the correct localized URL and take your routing settings into account (including base, trailingSlash, build.format, and site).[1]

---
import { getRelativeLocaleUrl, getAbsoluteLocaleUrl } from 'astro:i18n';

const locale = Astro.currentLocale ?? 'en';
---

<!-- Locale-aware internal link (relative path) -->
<a href={getRelativeLocaleUrl(locale, 'getting-started')}>Getting started</a>

<!-- Absolute URL (requires `site` in astro.config) -->
<a href={getAbsoluteLocaleUrl(locale, 'getting-started')}>Getting started</a>

• getRelativeLocaleUrl(locale, path) → localized path (e.g. /zh-cn/about).[2]
• getAbsoluteLocaleUrl(locale, path) → localized absolute URL when site is set; otherwise it falls back to a relative URL.[1]

2) In Starlight, use built-in route data when you just need “home for this locale”

Starlight exposes siteTitleHref, which already includes the current locale (e.g. /en/, /zh-cn/).[3]

3) About “absolute href links” + base

If your concern is deploy subpaths (Astro base), note that base does not automatically modify plain <a href="/"> in output (it’s a common gotcha).[4] Using the i18n helpers above is the most robust fix because they’re designed to generate correct URLs under your configured routing/base settings.[1]

Sources: Astro i18n API (astro:i18n).[1] Starlight i18n guide (uses Astro.currentLocale + getRelativeLocaleUrl).[2] Starlight route data (siteTitleHref).[3] Astro issue discussing base not rewriting anchor href.[4]

---

🏁 Script executed:

# First, let's check if LinkCard is a custom component and how it handles hrefs
find . -type f \( -name "*.astro" -o -name "*.tsx" -o -name "*.ts" -o -name "*.jsx" -o -name "*.js" \) | xargs grep -l "LinkCard" | head -20

Repository: Cap-go/website

Length of output: 40

---

🏁 Script executed:

# Check the Starlight/Astro configuration for locale settings
find . -type f \( -name "astro.config.*" -o -name "tsconfig.json" \) | head -10

Repository: Cap-go/website

Length of output: 92

---

🏁 Script executed:

# Look at other French docs pages to see how they handle internal links
find . -path "*/fr/docs/*" -name "*.mdx" -o -name "*.md" | head -10

Repository: Cap-go/website

Length of output: 392

---

🏁 Script executed:

# Search for LinkCard usage patterns in the codebase to understand how paths are handled
rg "LinkCard" -A 3 -B 1 --type astro --type typescript --type markdown | head -50

Repository: Cap-go/website

Length of output: 87

---

🏁 Script executed:

cat -n astro.config.mjs

Repository: Cap-go/website

Length of output: 50370

---

🏁 Script executed:

# Search for LinkCard component in all file types
rg "export.*LinkCard|const LinkCard|function LinkCard" -t ts -t tsx -t js -t jsx

Repository: Cap-go/website

Length of output: 85

---

🏁 Script executed:

# Look at one of the French docs pages to see actual link patterns
cat -n src/content/docs/fr/docs/live-updates/integrations/index.mdx | head -50

Repository: Cap-go/website

Length of output: 2479

---

🏁 Script executed:

# Search for how other French pages handle internal links
rg "href=" src/content/docs/fr/ -A 1 | head -30

Repository: Cap-go/website

Length of output: 2060

---

🏁 Script executed:

# Check if the target pages exist in French
find src/content/docs -path "*fr*" -name "azure-devops.mdx" -o -path "*fr*" -name "gitlab-ci.mdx" -o -path "*fr*" -name "github-actions.mdx"

Repository: Cap-go/website

Length of output: 448

---

🏁 Script executed:

# Look for any locale routing middleware or path handlers
rg "getRelativeLocaleUrl|getAbsoluteLocaleUrl|locale.*href|href.*locale" -t ts -t js -t astro --max-count 20

Repository: Cap-go/website

Length of output: 87

---

🏁 Script executed:

# Check locale service to understand how locales are configured
cat -n src/services/locale.ts 2>/dev/null || cat -n src/services/locale.js 2>/dev/null || find src -name "locale.*" -type f

Repository: Cap-go/website

Length of output: 668

---

🌐 Web query:

astro-i18n-aut automatic locale routing absolute paths how does it work

💡 Result:

astro-i18n-aut’s “automatic locale routing” works by generating additional localized versions of your existing src/pages/*.astro routes, without you manually duplicating files into src/pages/es/..., src/pages/fr/..., etc. Concretely, it duplicates your src/pages folder into temporary locale-specific folders and uses Astro’s injectRoute as a workaround to make Astro build the extra routes. It also uses middleware to handle things like redirecting the default-locale-prefixed URLs. [1], [2]

What routes get created

Given a page like src/pages/about.astro, it will render as: /about/, /es/about/, /fr/about/ etc. [1]

If redirectDefaultLocale is enabled, the library will redirect (example with default locale en): /en/about/ → /about/. [1]

“Absolute paths” and localized URLs (what you need to do)

astro-i18n-aut does not rewrite your links. So if you hardcode an absolute internal link like:

<a href="/about/">About</a>

…then on /es/... that link still points to the default-locale page (/about/), not /es/about/.

To generate the correct locale-prefixed path, use the helpers the package provides:

• getLocale(url) returns the current locale key (e.g. "/es/about" → "es", "/about" → "en"). [4]
• getLocaleUrl(url, locale) rewrites a URL to the chosen locale (e.g. getLocaleUrl("/about","es") → "/es/about"; getLocaleUrl("/es/about","en") → "/about"). [3]

So, typical usage in a page:

import { getLocale, getLocaleUrl } from "astro-i18n-aut";

const locale = getLocale(Astro.url);
const aboutInFrench = getLocaleUrl(Astro.url, "fr");

If you meant “absolute URL” (with domain)

If you need a fully qualified absolute URL (e.g. https://example.com/fr/about), Astro’s built-in i18n helper getAbsoluteLocaleUrl() does that when site is set in astro.config. [5]

Sources: GitHub README (routing + redirects) [1], npm README (how it works internally) [2], type definitions for getLocaleUrl/getLocale behavior [3], [4], Astro i18n API for absolute URLs [5].

---

🏁 Script executed:

# Check if there are English versions of these integration pages
find src/content/docs -name "azure-devops.mdx" -o -name "gitlab-ci.mdx" -o -name "github-actions.mdx" -o -name "bitbucket-pipeline.mdx"

Repository: Cap-go/website

Length of output: 1727

---

🏁 Script executed:

# Look at the English version of the integrations index to see how it handles links
find src/content/docs/en -path "*live-updates/integrations*" -name "*.mdx" | head -5

Repository: Cap-go/website

Length of output: 1727

---

🌐 Web query:

Starlight multilingual content routing absolute href links locale-aware MDX

💡 Result:

1) Multilingual content routing in Starlight

Configure locales in astro.config.mjs and place per-locale docs under matching folders in src/content/docs/<locale>/... (or use a root locale to avoid a URL prefix for one language). Starlight will then generate locale-prefixed routes and handle fallback behavior. [1]

2) Making absolute/leading-slash links locale-aware (especially in MDX)

A hard-coded MD/MDX link like:

[About](/about)

will always point to /about (no locale prefix). To generate locale-aware URLs, build the URL at runtime using Astro’s i18n helpers (which respect your i18n routing settings), e.g. getRelativeLocaleUrl() for site-relative links, or getAbsoluteLocaleUrl() if site is configured. [1][2]

In Starlight MDX, do it via a small component:

---
// src/components/LocaleLink.astro
import { getRelativeLocaleUrl } from 'astro:i18n';

const { to, ...attrs } = Astro.props;
const locale = Astro.currentLocale ?? 'en';
---
<a href={getRelativeLocaleUrl(locale, to)} {...attrs}><slot /></a>

Then in MDX:

import LocaleLink from '../../components/LocaleLink.astro';

<LocaleLink to="about">About</LocaleLink>

If you truly need fully-qualified URLs (e.g. for OG tags/emails), swap in getAbsoluteLocaleUrl() (it returns absolute URLs when site is set; otherwise it falls back to relative). [2]

3) Navigation-generated links

If you use Starlight’s sidebar config with slug entries, Starlight will generate localized internal links appropriately (and can translate labels/titles per locale). [3]

Sources: Starlight i18n guide [1], Astro astro:i18n URL helpers reference [2], Starlight sidebar i18n behavior [3].

---

Update href values to be locale-aware or include the /fr/ prefix for French content.

The hardcoded absolute paths (e.g., /docs/live-updates/integrations/azure-devops/) will resolve to the default English versions regardless of the current page's locale. In a Starlight multilingual setup using astro-i18n-aut, neither the integration library nor the LinkCard component automatically prepend the locale to absolute links.

To fix: either prefix paths with /fr/ (e.g., /fr/docs/live-updates/integrations/azure-devops/), or use Astro's getRelativeLocaleUrl() helper to generate locale-aware URLs at runtime.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@src/content/docs/fr/docs/live-updates/integrations/index.mdx` around lines 17
- 38, The LinkCard components use hardcoded absolute hrefs (e.g., in the
LinkCard entries for "Azure DevOps", "GitLab CI/CD", "GitHub Actions",
"Bitbucket Pipelines") which will always point to the default locale; update
those href props to be locale-aware by either prefixing each path with "/fr/"
for this French page (e.g., "/fr/docs/live-updates/integrations/azure-devops/")
or by generating the URL with the Astro/i18n helper (e.g., use
getRelativeLocaleUrl(...) when building the href passed into each LinkCard) so
links resolve to the correct locale at runtime.

[coderabbitai]

⚠️ Potential issue | 🟠 Major

Content is not French — page is English with scattered French terms

This file is located under the French locale path (fr/docs/) and has locale: fr in its frontmatter, but the body is written in English with random French words embedded mid-sentence (e.g., "Utilisateurs", "Appareils", "Construction", "Retour", "Précédent"). French-speaking users navigating to /fr/docs/live-updates/rollbacks/ will see primarily English content, defeating the localization goal described in this PR.

This appears to be an AI-generated file where French terms were inserted into English prose rather than producing a proper translation.

🧰 Tools

🪛 LanguageTool

[grammar] ~15-~15: Ensure spelling is correct
Context: ...omatic safety mechanisms. ## Automatic Restauration Protection Capgo includes a built-in s...

(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)

---

[grammar] ~19-~19: Ensure spelling is correct
Context: ...ous working version. ### How Automatic Restauration Works When a new update is downloaded ...

(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)

---

[grammar] ~62-~62: Ensure spelling is correct
Context: ...ase this value. ## Rolling Retour to a Précédent Bundle Every time you Télécharger a No...

(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)

---

[style] ~82-~82: You have already used this phrasing in nearby sentences. Consider replacing it to add variety to your writing.
Context: ...nal view. 5. Find the Construction you want to revert to in the Construction history. ...

(REP_WANT_TO_VB)

---

[style] ~86-~86: You have already used this phrasing in nearby sentences. Consider replacing it to add variety to your writing.
Context: ...ion for the Canal. 7. Confirm that you want to roll Retour to this Construction. </St...

(REP_WANT_TO_VB)

---

[style] ~96-~96: You have already used this phrasing in nearby sentences. Consider replacing it to add variety to your writing.
Context: ...e Canal view, find the Construction you want to revert to. 2. Click the crown icon Suiv...

(REP_WANT_TO_VB)

---

[style] ~98-~98: You have already used this phrasing in nearby sentences. Consider replacing it to add variety to your writing.
Context: ...select_bundle.webp) 3. Confirm that you want to roll Retour to this Construction. </St...

(REP_WANT_TO_VB)

---

[grammar] ~129-~129: Ensure spelling is correct
Context: ...inally packaged with your Application's Natif binary. This is known as the "built-in ...

(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@src/content/docs/fr/docs/live-updates/rollbacks.mdx` around lines 1 - 162,
The document has French frontmatter (locale: fr, title: Restaurations) but the
body is mostly English with scattered French tokens; replace the entire article
body with a proper French translation so the content matches locale: fr,
preserving technical identifiers and code samples (e.g., notifyAppReady(),
CapacitorUpdater) unchanged; translate UI labels, Steps items, Asides, image alt
text (e.g., "Restauration UI interface", "Canal management Options") and all
prose into fluent French, remove AI-artifact mixed-language phrases (e.g.,
"Retour", "Construction", "Appareils") by using correct French equivalents
consistently, and keep the structure and examples intact.

[coderabbitai]

⚠️ Potential issue | 🟠 Major

Content is not French — same English/French language mixing issue

The body is predominantly English with French terms scattered throughout. French users at /fr/docs/live-updates/update-behavior/ will see an English-language page.

🧰 Tools

🪛 LanguageTool

[grammar] ~59-~59: Ensure spelling is correct
Context: ...tly when an Mise à jour is applied. For Exemple, you might want to ensure a Utilisateur...

(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)

---

[style] ~80-~80: Some style guides suggest that commas should set off the year in a month-day-year date.
Context: ...ling an Mise à jour until after June 1, 2023 AND the Application has been background...

(MISSING_COMMA_AFTER_YEAR)

---

[style] ~97-~97: As an alternative to the over-used intensifier ‘very’, consider replacing this phrase.
Context: ...tely For critical updates or apps with very simple state, you may want to apply an update ...

(EN_WEAK_ADJECTIVE)

---

[style] ~102-~102: To elevate your writing, try using an alternative expression here.
Context: ...re actively using your app. Why this matters for Direct Updates: - **Faster Mises ...

(MATTERS_RELEVANT)

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@src/content/docs/fr/docs/live-updates/update-behavior.mdx` around lines 1 -
216, The page is marked locale: fr but the body is mostly English; translate the
entire document content into French, keeping the frontmatter locale: fr and the
existing headings (e.g., "Mise à jour Behavior", "Default Mise à jour Flow") and
components (<Steps>, <Aside>) intact; ensure all UI terms and examples (like
`setMultiDelay`, `directUpdate`, `autoSplashscreen`, `keepUrlPathAfterReload`,
code blocks, and links) are presented in French and fix consistent terminology
(use "Mise à jour"/"Mises à jour" uniformly), and update any in-text links or
captions (e.g., Delta Updates / differentials) to their French equivalents so
the /fr page is fully French.

[coderabbitai]

⚠️ Potential issue | 🔴 Critical

Broken internal link — French words in URL path will 404

The URL /docs/live-Mises à jour/differentials/ contains French words and spaces, making it an invalid URL path. The target file is at fr/docs/live-updates/differentials.mdx, so the URL should be /fr/docs/live-updates/differentials/.

✏️ Proposed fix

-Learn more in the [Delta Mises à jour Documentation](/docs/live-Mises à jour/differentials/).
+Learn more in the [Delta Updates Documentation](/fr/docs/live-updates/differentials/).

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	Learn more in the [Delta Mises à jour Documentation](/docs/live-Mises à jour/differentials/).
	Learn more in the [Delta Updates Documentation](/fr/docs/live-updates/differentials/).

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@src/content/docs/fr/docs/live-updates/update-behavior.mdx` at line 112, The
internal link in src/content/docs/fr/docs/live-updates/update-behavior.mdx
points to an invalid path with French characters and spaces; update the href in
the "Learn more in the [Delta Mises à jour Documentation](...)" link to the
correct canonical path /fr/docs/live-updates/differentials/ (keep the visible
link text as-is if desired) so the link resolves to
fr/docs/live-updates/differentials.mdx.