i18n

Manage translations by adopting a flat dot-notation key structure (module.feature.detail), maintaining synchronized locale files (en-US.json, zh-CN.json, zh-TW.json, ja-JP.json, ko-KR.json), and using t() function calls in your UI. This ensures consistent localization across all user-facing text.

Use a standardized flat dot-notation convention like module.feature.detail for all translation keys. This creates predictable, hierarchical naming that makes keys discoverable, reduces duplication, and simplifies maintenance across your codebase and locale files.

Hardcoded string detection identifies user-visible text embedded directly in your code that should be replaced with translation keys following the module.feature.detail pattern. Once detected, integrate t() calls to reference locale files instead of hard-coded values.

Yes, the workflow maintains consistency across multiple locale files including en-US.json, zh-CN.json, zh-TW.json, ja-JP.json, and ko-KR.json. Locale synchronization ensures every translation key exists in all files with matching structure.

Add new translation keys following the module.feature.detail naming convention, create entries in all active locale files simultaneously, then integrate t() calls in your components to reference the new keys. This keeps locales synchronized from the start.

Standardization prevents inconsistent key naming, locale drift, and missed translations. A defined workflow with flat-key conventions and synchronization checks ensures all user-facing text is properly localized, reducing bugs and scaling translation management as your application grows.