Translate navigation and shared documentation UI with GT - #350
Conversation
|
🕵
|
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
Blargian
added
the
docs-translations-all
Blargian
changed the title
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 6757853. Configure here.
| paths.push({ | ||
| params: { key: g.key }, | ||
| props: { items }, | ||
| props: { items, locale: tree.prefix[0] }, |
There was a problem hiding this comment.
Non-Latin nav labels collide lazy keys
High Severity
Translating navigation group and tab labels makes lazy sidebar keys collide for Japanese, Korean, Chinese, Arabic, and Russian. slugifyLabel keeps only a-z0-9, so those labels all become group, and tab names are omitted from the key path. getStaticPaths then throws on the duplicate, so locale builds that include those languages fail after GT writes translated navigation.
Additional Locations (2)
Reviewed by Cursor Bugbot for commit 6757853. Configure here.
1 participant
Restore the resolved navigation schema so GT can translate human-facing group, tab, item, anchor, and dropdown labels across referenced navigation files. Add a checked-in English UI dictionary for shared documentation chrome—including the top navigation, search and filter controls, page actions, table of contents, pagination, theme controls, and mobile navigation—and configure GT to generate its locale dictionaries. Navigation behavior now uses stable structure rather than translated English labels.
Add build-time guards for the GT translation contract and English navigation graph. The locale transform excludes Cloud OpenAPI operation pointers.
Expose every configured language from generated Cloud and ClickStack API operation pages. Locale-prefixed API routes render the English operation content with the localized untranslated-content notice until translated API content exists.
Use the existing
VERCEL_TRANSLATIONS_PROJECT_IDActions secret for preview and production translation deployments, including the reusable production workflow contract.Normalize non-standard and historical Shiki fence labels centrally so English and localized builds no longer emit missing-language diagnostics.
Validated with
pnpm run check:gt-navigation,pnpm run typecheck, and a focused Spanish translations build.Changelog category (leave one):
Changelog entry (a user-readable short description of the changes that goes into CHANGELOG.md):
Make documentation navigation, shared interface text, and generated API language routes available across locales, and normalize non-standard syntax-highlighting language labels.