i18n: tooling, drafts & CI guardrails
Open
Nobody has claimed this yet.
internationalization
- Dominant language
- Go
- Stars
- 432
- Forks
- 51
- PR merge metrics
- No merged PRs in 30d
Description
Part of the frontend internationalization effort (see Epic).
Tasks
- Add
eslint-plugin-i18next(opt-in per directory) to flag new hardcoded strings - CI script checking locale key parity across
en/es/fr/ja - Fill
es/fr/jaJSON with drafted (machine) translations for native refinement - Japanese (CJK) font/layout pass — verify rendering and that longer strings don't break layout (tray menu, dashboard cards)
- Document the i18n workflow in
docs/02-development-guide.md
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 by locating the frontend locale JSON files for en/es/fr/ja, the CI configuration, and docs/02-development-guide.md. Review the existing internationalization setup and determine how the lint rule, locale parity check, translations, Japanese layout checks, and workflow documentation fit together. Done means every checklist item is implemented and the locale, rendering, and CI checks pass.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- eslint, json
- Domain
- ci-cd, documentation, frontend, internationalization, localization, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100