Skip to content

Add comprehensive Live Update features documentation#478

Open
Pitiakova wants to merge 2 commits intomainfrom
val-update-types
Open

Add comprehensive Live Update features documentation#478
Pitiakova wants to merge 2 commits intomainfrom
val-update-types

Conversation

@Pitiakova
Copy link
Contributor

@Pitiakova Pitiakova commented Feb 16, 2026

Summary

  • Added comprehensive features documentation for Capgo Live Updates with 41 verified features
  • Organized features into 9 categories: Core Update System, Deployment Control, Developer Tools, Analytics & Monitoring, Security & Compliance, Team Collaboration, Platform Support, and Advanced Features
  • Translated documentation to all 8 supported languages (de, es, fr, id, it, ja, ko, zh)
  • Fixed documentation ordering: Features now appears after Overview and before Integrations
  • Updated Update Types ordering to appear after Features

Changes Made

New Files Created

  • docs/live-updates/features.mdx (English + 8 language translations)
    • 41 verified features with accurate descriptions
    • Links to detailed documentation for each feature
    • Dashboard locations where applicable
    • Usage examples for CLI/SDK features

Files Modified

  • docs/live-updates/update-types.mdx - Updated sidebar order from 2 to 3
  • docs/live-updates/integrations/index.mdx - Updated sidebar order from 3 to 4

Features Documented

Core Update System (5)

  • OTA Updates, Delta Updates, Automatic Rollback, Checksum Validation & Fallback, Breaking Update Detection

Deployment Control (3)

  • Channel System, Device Targeting, Channel Policies

Developer Tools (7)

  • Bundle Preview, Live Debugging, Bundle Manifest Viewer, Native Plugin Dependencies, CLI Integration, Bundle Encryption, Bundle Cleanup & Retention

Analytics & Monitoring (5)

  • Update Statistics, Device Logs, Bundle Usage Analytics, Channel Statistics, Deployment History

Security & Compliance (5)

  • End-to-End Encryption, Code Signing, SOC 2 Type II, App Store Compliance, 2FA Enforcement, Encrypted Bundles Enforcement

Team Collaboration (6)

  • RBAC, Audit Logs, Webhooks, Multi-User Collaboration, API Key Management, Password Policies

Platform Support (4)

  • Multi-Platform Support, Long-Term Support, Custom Storage Backends, China Configuration

Advanced Features (3)

  • Custom Update Behavior, Update Types, Credit System

Accuracy Improvements

  • ❌ Removed "Phased Rollouts" (not implemented)
  • ❌ Removed misleading "Self-Healing Updates" description
  • ✅ Corrected to "Checksum Validation & Fallback" (accurate)
  • ✅ Fixed "Custom Update Behavior" to reflect actual SDK options
  • ✅ Moved API Key Management and Password Policies to Team Collaboration section

Navigation Structure

Live Updates
├── Overview (order: 1)
├── Features (order: 2) ← NEW
├── Update Types (order: 3) ← moved
└── Integrations (order: 4) ← moved

Made with Cursor

Summary by CodeRabbit

  • New Features

    • Added "Update Types" section to the landing page with an interactive 4-card grid highlighting apply timing, delay conditions, version blocking, and delivery types.
  • Documentation

    • Added comprehensive "Update Types" reference documentation covering OTA update behaviors, configuration options, and examples across all supported languages.
    • Added "Features" catalog documenting all Capgo Live Updates capabilities, security, analytics, collaboration tools, and platform support.
    • Enhanced onboarding navigation with links to new update types documentation.

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Feb 16, 2026

📝 Walkthrough

Walkthrough

This pull request introduces a comprehensive new documentation section for OTA update types across all supported locales. It adds a new UpdateTypesSection Astro component to the homepage, creates parallel documentation pages for update types and features in English and 10 additional languages, updates navigation across onboarding and index pages, and adjusts sidebar ordering to accommodate the new content.

Changes

Cohort / File(s) Summary
Homepage Component Integration
src/components/landing/UpdateTypesSection.astro, src/pages/index.astro
New Astro component displaying a 4-card grid for update type features (Apply Timing, Delay Conditions, Version Blocking, Delivery Types) with hover styles and CTA link to docs. Integrated into homepage after GlobalInfrastructure section.
English Documentation - Update Types & Features
src/content/docs/docs/live-updates/update-types.mdx, src/content/docs/docs/live-updates/features.mdx
New comprehensive documentation pages: update-types covers apply timing, delay conditions, version blocking, and delivery types with code examples; features page catalogs all Capgo Live Updates capabilities with structured sections and links.
English Navigation & Sidebar Reordering
src/content/docs/docs/getting-started/onboarding.mdx, src/content/docs/docs/live-updates/index.mdx, src/content/docs/docs/live-updates/channels.mdx, src/content/docs/docs/live-updates/differentials.mdx, src/content/docs/docs/live-updates/update-behavior.mdx, src/content/docs/docs/live-updates/integrations/index.mdx
Added navigation cards linking to new update-types documentation in onboarding and index pages; adjusted sidebar order values (channels 2→3, differentials 4→5, update-behavior 3→4, integrations 1→4 with new label) to position new content in hierarchy.
German Documentation
src/content/docs/de/docs/getting-started/onboarding.mdx, src/content/docs/de/docs/live-updates/index.mdx, src/content/docs/de/docs/live-updates/update-types.mdx, src/content/docs/de/docs/live-updates/features.mdx
Parallel German locale pages: new update-types reference and features catalog with localized content; navigation links added to onboarding and index.
Spanish Documentation
src/content/docs/es/docs/getting-started/onboarding.mdx, src/content/docs/es/docs/live-updates/index.mdx, src/content/docs/es/docs/live-updates/update-types.mdx, src/content/docs/es/docs/live-updates/features.mdx
Parallel Spanish locale pages: localized update-types and features documentation with navigation updates.
French Documentation
src/content/docs/fr/getting-started/onboarding.mdx, src/content/docs/fr/live-updates/index.mdx, src/content/docs/fr/live-updates/update-types.mdx, src/content/docs/fr/docs/live-updates/features.mdx
Parallel French locale pages: localized documentation and navigation updates for update-types and features content.
Indonesian Documentation
src/content/docs/id/docs/getting-started/onboarding.mdx, src/content/docs/id/docs/live-updates/index.mdx, src/content/docs/id/docs/live-updates/update-types.mdx, src/content/docs/id/docs/live-updates/features.mdx
Parallel Indonesian locale pages with localized content and navigation links.
Italian Documentation
src/content/docs/it/docs/getting-started/onboarding.mdx, src/content/docs/it/docs/live-updates/index.mdx, src/content/docs/it/docs/live-updates/update-types.mdx, src/content/docs/it/docs/live-updates/features.mdx
Parallel Italian locale pages with localized update-types reference and features catalog.
Japanese Documentation
src/content/docs/ja/docs/getting-started/onboarding.mdx, src/content/docs/ja/docs/live-updates/index.mdx, src/content/docs/ja/docs/live-updates/update-types.mdx, src/content/docs/ja/docs/live-updates/features.mdx
Parallel Japanese locale pages with localized content and navigation integration.
Korean Documentation
src/content/docs/ko/docs/getting-started/onboarding.mdx, src/content/docs/ko/docs/live-updates/index.mdx, src/content/docs/ko/docs/live-updates/update-types.mdx, src/content/docs/ko/docs/live-updates/features.mdx
Parallel Korean locale pages with localized documentation and navigation updates.
Chinese Documentation
src/content/docs/zh/docs/getting-started/onboarding.mdx, src/content/docs/zh/docs/live-updates/index.mdx, src/content/docs/zh/docs/live-updates/update-types.mdx, src/content/docs/zh/docs/live-updates/features.mdx
Parallel Chinese locale pages with localized update-types reference and features content.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~25 minutes

Poem

🐰 Hop, skip, and a hop away,
New docs bloom in every locale today!
Update types shine with code so clear,
Features catalog all in here.
From Japanese to French we bound,
Documentation joy all around! 🌟

🚥 Pre-merge checks | ✅ 3 | ❌ 1

❌ Failed checks (1 warning)

Check name Status Explanation Resolution
Merge Conflict Detection ⚠️ Warning ❌ Merge conflicts detected (38 files):

⚔️ .github/workflows/deploy.yml (content)
⚔️ .github/workflows/typos.yml (content)
⚔️ bun.lock (content)
⚔️ package.json (content)
⚔️ src/components/ConditionalQuestionnaire.astro (content)
⚔️ src/components/FrameworkSelector.astro (content)
⚔️ src/content/docs/de/docs/getting-started/onboarding.mdx (content)
⚔️ src/content/docs/de/docs/live-updates/index.mdx (content)
⚔️ src/content/docs/docs/cli/cloud-build/android.mdx (content)
⚔️ src/content/docs/docs/cli/cloud-build/ios.mdx (content)
⚔️ src/content/docs/docs/cli/reference/app.mdx (content)
⚔️ src/content/docs/docs/cli/reference/build.mdx (content)
⚔️ src/content/docs/docs/cli/reference/bundle.mdx (content)
⚔️ src/content/docs/docs/cli/reference/channel.mdx (content)
⚔️ src/content/docs/docs/cli/reference/organisation.mdx (content)
⚔️ src/content/docs/docs/getting-started/onboarding.mdx (content)
⚔️ src/content/docs/docs/live-updates/channels.mdx (content)
⚔️ src/content/docs/docs/live-updates/differentials.mdx (content)
⚔️ src/content/docs/docs/live-updates/index.mdx (content)
⚔️ src/content/docs/docs/live-updates/integrations/index.mdx (content)
⚔️ src/content/docs/docs/live-updates/update-behavior.mdx (content)
⚔️ src/content/docs/es/docs/getting-started/onboarding.mdx (content)
⚔️ src/content/docs/es/docs/live-updates/index.mdx (content)
⚔️ src/content/docs/fr/getting-started/onboarding.mdx (content)
⚔️ src/content/docs/fr/live-updates/index.mdx (content)
⚔️ src/content/docs/id/docs/getting-started/onboarding.mdx (content)
⚔️ src/content/docs/id/docs/live-updates/index.mdx (content)
⚔️ src/content/docs/it/docs/getting-started/onboarding.mdx (content)
⚔️ src/content/docs/it/docs/live-updates/index.mdx (content)
⚔️ src/content/docs/ja/docs/getting-started/onboarding.mdx (content)
⚔️ src/content/docs/ja/docs/live-updates/index.mdx (content)
⚔️ src/content/docs/ko/docs/getting-started/onboarding.mdx (content)
⚔️ src/content/docs/ko/docs/live-updates/index.mdx (content)
⚔️ src/content/docs/zh/docs/getting-started/onboarding.mdx (content)
⚔️ src/content/docs/zh/docs/live-updates/index.mdx (content)
⚔️ src/css/docs.css (content)
⚔️ src/pages/index.astro (content)
⚔️ src/pages/subprocessors.astro (content)

These conflicts must be resolved before merging into main.
Resolve conflicts locally and push changes to this branch.
✅ 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 accurately describes the main change: comprehensive Live Update features documentation has been added across multiple files and languages, which is the primary focus of this PR.
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 val-update-types
⚔️ Resolve merge conflicts (beta)
  • Auto-commit resolved conflicts to branch val-update-types
  • Create stacked PR with resolved conflicts
  • Post resolved changes as copyable diffs in a comment

Tip

Issue Planner is now in beta. Read the docs and try it out! Share your feedback on Discord.


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

Comment @coderabbitai help to get the list of available commands and usage tips.

@sonarqubecloud
Copy link

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 8

Note

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

🤖 Fix all issues with AI agents
In `@src/content/docs/de/docs/live-updates/features.mdx`:
- Around line 1-11: The file's content (frontmatter keys title and description
and the body text "This page provides a comprehensive overview of all features
available in Capgo Live Updates. Each feature includes a brief description and
links to detailed documentation.") is still in English despite the German
locale; translate the title, description and all body copy into German, keeping
the existing frontmatter keys (title, description, sidebar, locale) and imports
(Card, CardGrid, Aside) unchanged, and ensure the translated strings replace the
English ones so the page matches other files in the de locale.

In `@src/content/docs/de/docs/live-updates/update-types.mdx`:
- Around line 1-6: Fix the frontmatter sidebar ordering in the file (title:
Update-Typen) by changing the sidebar.order value from 2 to 3 so it no longer
conflicts with features.mdx; locate the top YAML block (the --- delimited
frontmatter) and update the "sidebar: order: 2" entry to "sidebar: order: 3".

In `@src/content/docs/es/docs/live-updates/features.mdx`:
- Around line 1-11: The page at features.mdx is marked locale: es but the
frontmatter title/description and entire body are in English; update the title,
description, headings, and all prose to Spanish to match the Spanish locale and
existing translated pages (e.g., compare with update-types.mdx for tone and
terminology), ensuring imported components (Card, CardGrid, Aside) remain
unchanged and any internal links point to Spanish docs; also run a quick grep
for other English strings in this file and replace them with proper Spanish
translations.

In `@src/content/docs/fr/docs/live-updates/features.mdx`:
- Around line 1-11: The file declares locale: fr but contains English content;
update the frontmatter keys (title and description) and the page body to French
(or move the file to the English locale if English is intended) so locale
matches content; specifically translate the frontmatter "title" and
"description" and the body text starting with "This page provides..." into
French and ensure the "locale" value remains "fr"; apply the same fix to other
non-English locale feature pages (e.g., files with locale: ko, ja) so each
file's locale value matches its translated content.

In `@src/content/docs/it/docs/live-updates/features.mdx`:
- Around line 1-11: The file's frontmatter and body are in English while the
locale is set to it; update the frontmatter keys (title and description) and the
page content to Italian to match the Italian locale and sibling translations
(e.g., translate the title: "Features" and description string, plus the body
sentence starting "This page provides..."); preserve the import statements and
frontmatter structure (including locale: it) and ensure the translated text
reads naturally in Italian and follows the same wording/style used in the
sibling file update-types.mdx.

In `@src/content/docs/it/docs/live-updates/update-types.mdx`:
- Around line 4-6: The sidebar frontmatter in the non-English translations of
update-types.mdx still sets "order: 2", causing a conflict with features.mdx;
update the frontmatter value from "order: 2" to "order: 3" in each translated
update-types.mdx (Italian, French, German, Japanese, Korean, Indonesian,
Spanish, Chinese) so Update Types appears after Features; ensure you only change
the top-level "sidebar: order" value and keep the rest of the frontmatter
intact.

In `@src/content/docs/ko/docs/live-updates/update-types.mdx`:
- Around line 1-6: The frontmatter in update-types.mdx for non-English locales
has sidebar.order set to 2; update the YAML frontmatter key "sidebar: order" in
each translated file named update-types.mdx (Korean, Chinese, Japanese,
Indonesian, Spanish, Italian, French, German) to 3 to match the English version
and the intended navigation order (Overview=1, Features=2, Update Types=3,
Integrations=4); locate the top-of-file YAML block (the lines starting with ---
and the "sidebar:" mapping) and change the value from 2 to 3 in each language
copy.

In `@src/content/docs/zh/docs/live-updates/features.mdx`:
- Around line 1-11: The frontmatter declares locale: zh for this file (title:
Features) but the body text is still in English; translate the page content into
Chinese to match the zh locale and the style of other translated pages (e.g.,
the parallel update-types.mdx). Update the prose after the imports (the sentence
starting "This page provides a comprehensive overview...") and any other English
strings in the document to Chinese, preserving the existing frontmatter keys
(title, description, sidebar, locale) and the imported components (Card,
CardGrid, Aside) and keeping link structure and component usage identical.
🟡 Minor comments (13)
src/content/docs/docs/live-updates/update-types.mdx-76-78 (1)

76-78: ⚠️ Potential issue | 🟡 Minor

CLI command is missing the app ID argument.

Compared to the equivalent example in channels.mdx (npx @capgo/cli@latest channel set production com.example.app --disable-auto-update major), this command omits the app ID and the @latest tag. Users copying this will get an error.

Proposed fix
-npx `@capgo/cli` channel set production --disable-auto-update major
+npx `@capgo/cli`@latest channel set production com.example.app --disable-auto-update major
src/content/docs/docs/live-updates/update-behavior.mdx-4-5 (1)

4-5: ⚠️ Potential issue | 🟡 Minor

Sidebar order collisions: multiple files share the same order values.

  • Order 3: channels.mdx and update-types.mdx
  • Order 4: update-behavior.mdx and integrations/index.mdx
  • Order 5: differentials.mdx, encryption.mdx, and rollbacks.mdx
  • Order 6: compliance.mdx and custom-storage.mdx

Starlight resolves same-order items alphabetically, which may not produce the intended navigation sequence. Assign unique order values to each sibling page.

src/content/docs/zh/docs/live-updates/update-types.mdx-4-6 (1)

4-6: ⚠️ Potential issue | 🟡 Minor

Sidebar order should be 3, not 2.

Same conflict as the Spanish locale: both features.mdx and update-types.mdx have order: 2. Per the intended navigation (Overview → Features → Update Types → Integrations), this should be order: 3.

Proposed fix
 sidebar:
-  order: 2
+  order: 3
src/components/landing/UpdateTypesSection.astro-28-30 (1)

28-30: ⚠️ Potential issue | 🟡 Minor

Decorative SVGs are missing aria-hidden="true".

All five SVGs in this component (four card icons + the CTA arrow) are decorative — they don't convey information beyond the adjacent text. Per coding guidelines, decorative SVGs must have aria-hidden="true".

Example fix for one SVG (apply to all five)
-            <svg class="w-8 h-8 text-blue-400" fill="none" viewBox="0 0 24 24" stroke="currentColor" stroke-width="1.5">
+            <svg class="w-8 h-8 text-blue-400" fill="none" viewBox="0 0 24 24" stroke="currentColor" stroke-width="1.5" aria-hidden="true">

As per coding guidelines: "Decorative SVGs must have aria-hidden="true"".

Also applies to: 43-45, 58-61, 74-76, 94-96

src/content/docs/es/docs/live-updates/update-types.mdx-4-6 (1)

4-6: ⚠️ Potential issue | 🟡 Minor

Sidebar order conflicts with features.mdx — should be order: 3.

Both this file and features.mdx (es locale) have sidebar.order: 2. Per the PR objectives, the intended navigation order is: Overview (1) → Features (2) → Update Types (3) → Integrations (4). This will cause unpredictable sidebar ordering.

Proposed fix
 sidebar:
-  order: 2
+  order: 3
src/content/docs/ja/docs/getting-started/onboarding.mdx-529-531 (1)

529-531: ⚠️ Potential issue | 🟡 Minor

Inconsistent localization: new card is in Japanese while all surrounding cards are in English.

The "アップデートタイプ" card (lines 529-531) is localized to Japanese, but the adjacent cards ("Deploy Updates", "CI/CD Integration", "Channels", "Encryption", "Update Behavior") remain in English. This creates a visually inconsistent experience in the same CardGrid. Either localize all cards or keep them all in English for consistency within this section.

src/content/docs/fr/live-updates/update-types.mdx-4-6 (1)

4-6: ⚠️ Potential issue | 🟡 Minor

Sidebar order conflict: this should be order: 3.

Per the PR objectives, the navigation order should be: Overview (1) → Features (2) → Update Types (3) → Integrations (4). Both this file and features.mdx currently have order: 2, which will cause unpredictable sidebar ordering.

Proposed fix
 sidebar:
-  order: 2
+  order: 3
src/content/docs/zh/docs/getting-started/onboarding.mdx-529-531 (1)

529-531: ⚠️ Potential issue | 🟡 Minor

Inconsistent localization: only this card is in Chinese while all others are in English.

The new card uses Chinese title and description ("更新类型"), but every other card in this CardGrid (lines 526–543) remains in English. Either localize all cards or keep this one in English to match the rest of the page.

src/content/docs/ko/docs/getting-started/onboarding.mdx-529-531 (1)

529-531: ⚠️ Potential issue | 🟡 Minor

Inconsistent localization: only this card is in Korean while all others are in English.

Same pattern as the zh and id onboarding pages. The new card uses Korean ("업데이트 유형") but all sibling cards remain in English. Align the language for a consistent user experience.

src/content/docs/id/docs/getting-started/onboarding.mdx-529-531 (1)

529-531: ⚠️ Potential issue | 🟡 Minor

Inconsistent localization: only this card is in Indonesian while all others are in English.

Same issue as the zh onboarding page — the new card uses Indonesian ("Jenis Update") but every sibling card remains in English. Align the language across all cards.

src/content/docs/es/docs/live-updates/index.mdx-70-74 (1)

70-74: ⚠️ Potential issue | 🟡 Minor

New card looks good, but existing sibling links appear broken.

The new "Tipos de Actualización" card is properly localized and links to the correct path. However, the surrounding unchanged cards (lines 76, 82, 88, 93) use translated URL paths like /docs/live-Actualizaciones/Canales/ instead of the expected English paths (/docs/live-updates/channels/, etc.), which will likely 404. Consider fixing those in this PR for consistency.

src/content/docs/it/docs/getting-started/onboarding.mdx-529-531 (1)

529-531: ⚠️ Potential issue | 🟡 Minor

Language inconsistency: Italian card text on an otherwise English page.

The rest of this Italian-locale onboarding page has English content (titles, descriptions, all other cards). The new "Tipi di Aggiornamento" card is the only element written in Italian, which creates a jarring inconsistency. Either translate the entire page to Italian or keep this card in English to match the surrounding content.

-  <a href="/docs/live-updates/update-types/"><Card title="Tipi di Aggiornamento" icon="book">
-    Riferimento di tutti i tipi di aggiornamento OTA: tempistiche di applicazione, condizioni di ritardo, blocco versioni e distribuzione
+  <a href="/docs/live-updates/update-types/"><Card title="Update Types" icon="book">
+    Reference of all OTA update types: apply timing, delay conditions, version blocking, and delivery
src/content/docs/it/docs/live-updates/features.mdx-286-326 (1)

286-326: ⚠️ Potential issue | 🟡 Minor

Feature count mismatch: Security & Compliance lists 6 items, PR objectives say 5.

The PR objectives state "Security & Compliance (5)" but this section contains 6 features: End-to-End Encryption, Code Signing, SOC 2 Type II, App Store Compliance, 2FA Enforcement, and Encrypted Bundles Enforcement. The PR summary text itself lists all 6, so the count "(5)" in the objectives appears to be the error — but worth confirming intent.

🧹 Nitpick comments (5)
src/content/docs/docs/live-updates/update-types.mdx (1)

93-99: Inconsistent CLI version tags — missing @latest.

Other docs consistently use @capgo/cli@latest. Consider aligning for consistency.

Proposed fix
 # Full bundle (default)
-npx `@capgo/cli` bundle upload --channel production
+npx `@capgo/cli`@latest bundle upload --channel production
 
 # Delta updates
-npx `@capgo/cli` bundle upload --channel production --delta
+npx `@capgo/cli`@latest bundle upload --channel production --delta
src/content/docs/es/docs/live-updates/features.mdx (1)

9-9: Unused imports: Card and CardGrid are never used.

Only Aside would be potentially useful (though it's not used either). None of these imported components appear in the page body.

Proposed fix
-import { Card, CardGrid, Aside } from '@astrojs/starlight/components';

Remove the import entirely, or keep only what's actually used once content is finalized.

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

8-8: Unused imports: Card, CardGrid, and Aside are not referenced anywhere in the page.

These components are imported but never used in the body. This applies to all locale copies of this file as well.

Proposed fix
-import { Card, CardGrid, Aside } from '@astrojs/starlight/components';
src/content/docs/fr/live-updates/update-types.mdx (1)

25-32: Code comments are in English in a French documentation page.

The inline comments (// default, // or: ...) should be localized to French for consistency with the rest of the page.

Proposed fix
     directUpdate: false, // default
-    // or: 'atInstall' | 'onLaunch' | 'always'
+    // ou : 'atInstall' | 'onLaunch' | 'always'
src/content/docs/fr/docs/live-updates/features.mdx (1)

9-9: Unused imports: Card and CardGrid are never used in this file.

Only Aside would potentially be used, but it's not referenced either. Remove unused imports.

Proposed fix
-import { Card, CardGrid, Aside } from '@astrojs/starlight/components';

Comment on lines +1 to +11
---
title: Features
description: "Complete reference of all Capgo Live Update capabilities, from core update system to advanced deployment controls, analytics, and team collaboration features."
sidebar:
order: 2
locale: de
---

import { Card, CardGrid, Aside } from '@astrojs/starlight/components';

This page provides a comprehensive overview of all features available in Capgo Live Updates. Each feature includes a brief description and links to detailed documentation.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟠 Major

Untranslated content: entire page is in English despite being in the German (de) locale.

This file is located under src/content/docs/de/ but the title, description, and all body content are in English. Other German pages in this PR (e.g., onboarding.mdx, update-types.mdx) are properly translated. This page should be translated to German to match the other locale files in this PR.

🤖 Prompt for AI Agents
In `@src/content/docs/de/docs/live-updates/features.mdx` around lines 1 - 11, The
file's content (frontmatter keys title and description and the body text "This
page provides a comprehensive overview of all features available in Capgo Live
Updates. Each feature includes a brief description and links to detailed
documentation.") is still in English despite the German locale; translate the
title, description and all body copy into German, keeping the existing
frontmatter keys (title, description, sidebar, locale) and imports (Card,
CardGrid, Aside) unchanged, and ensure the translated strings replace the
English ones so the page matches other files in the de locale.

Comment on lines +1 to +6
---
title: Update-Typen
description: "Eine umfassende Referenz aller OTA-Update-Typen, die Capgo bereitstellt: Anwendungszeitpunkt, Verzögerungsbedingungen, Versionssperrung und Bereitstellungsmethoden."
sidebar:
order: 2
---
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟠 Major

Sidebar order conflict: should be 3, not 2.

Same issue as the Korean locale file — this conflicts with features.mdx which also has order: 2. Per PR objectives, Update Types should be order: 3.

Proposed fix
 sidebar:
-  order: 2
+  order: 3
📝 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
---
title: Update-Typen
description: "Eine umfassende Referenz aller OTA-Update-Typen, die Capgo bereitstellt: Anwendungszeitpunkt, Verzögerungsbedingungen, Versionssperrung und Bereitstellungsmethoden."
sidebar:
order: 2
---
---
title: Update-Typen
description: "Eine umfassende Referenz aller OTA-Update-Typen, die Capgo bereitstellt: Anwendungszeitpunkt, Verzögerungsbedingungen, Versionssperrung und Bereitstellungsmethoden."
sidebar:
order: 3
---
🤖 Prompt for AI Agents
In `@src/content/docs/de/docs/live-updates/update-types.mdx` around lines 1 - 6,
Fix the frontmatter sidebar ordering in the file (title: Update-Typen) by
changing the sidebar.order value from 2 to 3 so it no longer conflicts with
features.mdx; locate the top YAML block (the --- delimited frontmatter) and
update the "sidebar: order: 2" entry to "sidebar: order: 3".

Comment on lines +1 to +11
---
title: Features
description: "Complete reference of all Capgo Live Update capabilities, from core update system to advanced deployment controls, analytics, and team collaboration features."
sidebar:
order: 2
locale: es
---

import { Card, CardGrid, Aside } from '@astrojs/starlight/components';

This page provides a comprehensive overview of all features available in Capgo Live Updates. Each feature includes a brief description and links to detailed documentation.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟠 Major

Content is not translated to Spanish.

This file is located under src/content/docs/es/ (Spanish locale) and has locale: es in frontmatter, but the entire page body — title, description, headings, and all prose — is in English. Compare with update-types.mdx in the same locale, which is properly translated. This undermines the localization effort described in the PR objectives.

🤖 Prompt for AI Agents
In `@src/content/docs/es/docs/live-updates/features.mdx` around lines 1 - 11, The
page at features.mdx is marked locale: es but the frontmatter title/description
and entire body are in English; update the title, description, headings, and all
prose to Spanish to match the Spanish locale and existing translated pages
(e.g., compare with update-types.mdx for tone and terminology), ensuring
imported components (Card, CardGrid, Aside) remain unchanged and any internal
links point to Spanish docs; also run a quick grep for other English strings in
this file and replace them with proper Spanish translations.

Comment on lines +1 to +11
---
title: Features
description: "Complete reference of all Capgo Live Update capabilities, from core update system to advanced deployment controls, analytics, and team collaboration features."
sidebar:
order: 2
locale: fr
---

import { Card, CardGrid, Aside } from '@astrojs/starlight/components';

This page provides a comprehensive overview of all features available in Capgo Live Updates. Each feature includes a brief description and links to detailed documentation.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟠 Major

Entire page content is in English despite being in the French (fr) locale directory.

This file is at src/content/docs/fr/docs/live-updates/features.mdx with locale: fr, but the title, description, and all body text are in English. This defeats the purpose of localization and will confuse French-speaking users who expect translated content. The same issue applies to all other non-English locale feature pages (ko, ja, etc.) in this PR.

🤖 Prompt for AI Agents
In `@src/content/docs/fr/docs/live-updates/features.mdx` around lines 1 - 11, The
file declares locale: fr but contains English content; update the frontmatter
keys (title and description) and the page body to French (or move the file to
the English locale if English is intended) so locale matches content;
specifically translate the frontmatter "title" and "description" and the body
text starting with "This page provides..." into French and ensure the "locale"
value remains "fr"; apply the same fix to other non-English locale feature pages
(e.g., files with locale: ko, ja) so each file's locale value matches its
translated content.

Comment on lines +1 to +11
---
title: Features
description: "Complete reference of all Capgo Live Update capabilities, from core update system to advanced deployment controls, analytics, and team collaboration features."
sidebar:
order: 2
locale: it
---

import { Card, CardGrid, Aside } from '@astrojs/starlight/components';

This page provides a comprehensive overview of all features available in Capgo Live Updates. Each feature includes a brief description and links to detailed documentation.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟠 Major

Entire file is in English despite being in the Italian locale directory.

This file is located at src/content/docs/it/docs/live-updates/features.mdx but all content — title, description, and body — is in English. The sibling update-types.mdx in the same Italian directory is properly translated, so this appears to be an oversight. The content should be translated to Italian to match the other locale files.

🤖 Prompt for AI Agents
In `@src/content/docs/it/docs/live-updates/features.mdx` around lines 1 - 11, The
file's frontmatter and body are in English while the locale is set to it; update
the frontmatter keys (title and description) and the page content to Italian to
match the Italian locale and sibling translations (e.g., translate the title:
"Features" and description string, plus the body sentence starting "This page
provides..."); preserve the import statements and frontmatter structure
(including locale: it) and ensure the translated text reads naturally in Italian
and follows the same wording/style used in the sibling file update-types.mdx.

Comment on lines +4 to +6
sidebar:
order: 2
---
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟠 Major

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
# Verify sidebar order values across all locales for update-types and features
echo "=== update-types.mdx sidebar orders (all locales) ==="
fd 'update-types.mdx' src/content/docs --exec sh -c 'echo "File: $1"; head -6 "$1"' _ {}

echo ""
echo "=== features.mdx sidebar orders (all locales) ==="
fd 'features.mdx' src/content/docs --exec sh -c 'echo "File: $1"; head -6 "$1"' _ {}

Repository: Cap-go/website

Length of output: 4974


Sidebar order conflict: update-types.mdx in all non-English locales still has order: 2, conflicting with features.mdx.

The English version was correctly updated to order: 3, but all translations (Italian, French, German, Japanese, Korean, Indonesian, Spanish, Chinese) remain at order: 2. Per the PR objectives, Update Types should appear after Features; update all non-English locale versions to order: 3.

Fix for this file
 sidebar:
-  order: 2
+  order: 3
📝 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
sidebar:
order: 2
---
sidebar:
order: 3
---
🤖 Prompt for AI Agents
In `@src/content/docs/it/docs/live-updates/update-types.mdx` around lines 4 - 6,
The sidebar frontmatter in the non-English translations of update-types.mdx
still sets "order: 2", causing a conflict with features.mdx; update the
frontmatter value from "order: 2" to "order: 3" in each translated
update-types.mdx (Italian, French, German, Japanese, Korean, Indonesian,
Spanish, Chinese) so Update Types appears after Features; ensure you only change
the top-level "sidebar: order" value and keep the rest of the frontmatter
intact.

Comment on lines +1 to +6
---
title: 업데이트 유형
description: "Capgo가 제공하는 모든 OTA 업데이트 유형에 대한 포괄적인 참조: 적용 시점, 지연 조건, 버전 차단 및 전달 방법."
sidebar:
order: 2
---
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟠 Major

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
# Verify sidebar order across all update-types.mdx and features.mdx files
echo "=== update-types.mdx sidebar orders ==="
fd 'update-types.mdx' src/content/docs --exec grep -H 'order:' {}

echo ""
echo "=== features.mdx sidebar orders ==="
fd 'features.mdx' src/content/docs --exec grep -H 'order:' {}

Repository: Cap-go/website

Length of output: 1275


Sidebar order conflict: should be 3, not 2.

This affects all non-English language versions of update-types.mdx (Korean, Chinese, Japanese, Indonesian, Spanish, Italian, French, German). The English version was correctly updated to order 3, but the translations are still at order 2. Per PR objectives, the navigation order should be: Overview (1), Features (2), Update Types (3), Integrations (4). Update all language-specific update-types.mdx files from order: 2 to order: 3 to maintain consistency with the English version.

Proposed fix
 sidebar:
-  order: 2
+  order: 3

Apply to: src/content/docs/ko/docs/live-updates/update-types.mdx and all other language variants (zh, ja, id, es, it, fr, de).

📝 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
---
title: 업데이트 유형
description: "Capgo가 제공하는 모든 OTA 업데이트 유형에 대한 포괄적인 참조: 적용 시점, 지연 조건, 버전 차단 및 전달 방법."
sidebar:
order: 2
---
---
title: 업데이트 유형
description: "Capgo가 제공하는 모든 OTA 업데이트 유형에 대한 포괄적인 참조: 적용 시점, 지연 조건, 버전 차단 및 전달 방법."
sidebar:
order: 3
---
🤖 Prompt for AI Agents
In `@src/content/docs/ko/docs/live-updates/update-types.mdx` around lines 1 - 6,
The frontmatter in update-types.mdx for non-English locales has sidebar.order
set to 2; update the YAML frontmatter key "sidebar: order" in each translated
file named update-types.mdx (Korean, Chinese, Japanese, Indonesian, Spanish,
Italian, French, German) to 3 to match the English version and the intended
navigation order (Overview=1, Features=2, Update Types=3, Integrations=4);
locate the top-of-file YAML block (the lines starting with --- and the
"sidebar:" mapping) and change the value from 2 to 3 in each language copy.

Comment on lines +1 to +11
---
title: Features
description: "Complete reference of all Capgo Live Update capabilities, from core update system to advanced deployment controls, analytics, and team collaboration features."
sidebar:
order: 2
locale: zh
---

import { Card, CardGrid, Aside } from '@astrojs/starlight/components';

This page provides a comprehensive overview of all features available in Capgo Live Updates. Each feature includes a brief description and links to detailed documentation.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟠 Major

Content is not translated to Chinese.

Same issue as the Spanish locale: this file is under src/content/docs/zh/ with locale: zh, but all content is in English. The parallel update-types.mdx in this locale is properly translated to Chinese, so this page should follow the same pattern.

🤖 Prompt for AI Agents
In `@src/content/docs/zh/docs/live-updates/features.mdx` around lines 1 - 11, The
frontmatter declares locale: zh for this file (title: Features) but the body
text is still in English; translate the page content into Chinese to match the
zh locale and the style of other translated pages (e.g., the parallel
update-types.mdx). Update the prose after the imports (the sentence starting
"This page provides a comprehensive overview...") and any other English strings
in the document to Chinese, preserving the existing frontmatter keys (title,
description, sidebar, locale) and the imported components (Card, CardGrid,
Aside) and keeping link structure and component usage identical.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant