i18n: set up i18next infrastructure
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 432
- Forks
- 51
- PR merge metrics
- No merged PRs in 30d
Description
Part of the frontend internationalization effort (see Epic).
Stand up the i18n foundation so all later string extraction has somewhere to go.
Tasks
- Add deps:
react-i18next,i18next,i18next-browser-languagedetector - Create
src/frontend/src/i18n/index.ts(i18next init for the renderer) - Create locale folders/namespaces:
src/frontend/src/i18n/locales/{en,es,fr,ja}/{common,settings,dashboard,onboarding,activity,mappings,about}.json - Wrap
<AppShell />inindex.js(I18nextProvider or side-effect import) - Default language from
navigator.language, fallback toen
Locales
en (base) · es · fr · ja. Non-English files start as drafts to be refined by native speakers.
No visible UI change expected from this issue alone.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the frontend entrypoint index.js and create the i18n setup at src/frontend/src/i18n/index.ts. Add the four locale directories and listed namespaces, then connect the renderer to AppShell with the specified provider or import. Done means the dependencies, language detection with an en fallback, and all requested locale files are present; no visible UI change is expected.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, react, typescript
- Domain
- frontend, internationalization
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Clearly specified
- Newbie friendliness
- 64/100