Problem statement
The UI currently lacks any localization/internationalization infrastructure. All user-facing text is hardcoded in English, making the app inaccessible to non-English users.
Proposed solution
Introduce an i18n library (e.g., react-i18next or FormatJS) and externalize all static strings into locale files per language.
Alternatives considered
- Rolling a custom i18n utility (more maintenance burden)
- Using browser-native Intl only (doesn't cover UI string translation)
Area
UI (apps/ui/)
Priority
Critical
Additional context
Requires a locale file structure, language detection, and a language switcher in the UI.
Problem statement
The UI currently lacks any localization/internationalization infrastructure. All user-facing text is hardcoded in English, making the app inaccessible to non-English users.
Proposed solution
Introduce an i18n library (e.g., react-i18next or FormatJS) and externalize all static strings into locale files per language.
Alternatives considered
Area
UI (
apps/ui/)Priority
Critical
Additional context
Requires a locale file structure, language detection, and a language switcher in the UI.