Add localization (i18n) support #15
Description
Summary
Introduce a localization (i18n) framework and wiring so the editor can support multiple languages in the future, while shipping English-only strings for MVP.
Goals
- Establish a consistent way to manage UI strings (no hardcoded text in components).
- Enable future localization by centralizing message definitions and lookup.
- Provide an English locale as the default and only shipped locale for now.
Non-Goals
- Translating the UI into additional languages for MVP.
Description
Add i18n scaffolding across the editor UI:
- Add an i18n library and baseline configuration.
- Define a locales/ structure and an English message bundle.
- Provide an i18n provider at the app/editor root so all UI components can access translated strings.
- Provide a simple pattern for contributors:
- how to add a new string
- how to reference it in components
- naming conventions for keys
Testing
- Unit test or smoke test that the editor renders with the i18n provider enabled.
- Manual verification: UI renders without missing-key errors and no fallback “raw keys” appear.