976 B
ADR-025: Internationalization (i18n) and Localization (l10n) Strategy
Date: 2025-12-12
Status: Proposed
Context
The application currently displays all text, dates, and currency in a single format (likely English/USD). To expand its user base, it will need to support multiple languages and regional formats.
Decision
We will adopt a framework for internationalization. For the frontend, this will involve a library like react-i18next to manage translation files (e.g., en.json, es.json). For the backend, it will define how to handle locale-specific data (like currency formatting in API responses) and store user language preferences.
Consequences
Positive: Lays the architectural groundwork for future global expansion. Improves user experience for non-English speakers. Negative: Requires significant effort to translate all user-facing text. Adds complexity to both frontend and backend code for handling locale-specific data.