i18n localization roadmap: official status and community execution path

Why this page exists

i18n is a persistent demand, but most teams lack execution structure.
This page turns localization from ad-hoc edits into a maintainable workflow.

Reference:

• Issue #3460

Four-stage roadmap

Stage 1: status mapping

1. map pages already localized
2. map system prompts still monolingual
3. map error messages without localization

Stage 2: terminology baseline

1. maintain one glossary for core terms such as Pairing, Session, Plugin
2. define non-translatable and translatable boundaries
3. align glossary before translation starts

Stage 3: publishing workflow

1. split copy by module, avoid giant batch edits
2. include source context for every translation change
3. ship in small batches, starting from high-traffic pages

Stage 4: regression and quality

1. verify route mapping parity
2. verify locale switch lands on equivalent page
3. verify SEO title and description parity

Minimum team roles

1. glossary owner for terminology consistency
2. translator for first-pass content
3. reviewer for semantic and style consistency
4. verifier for routing, SEO, and readability checks

Pass criteria

1. core pages have parity in language switch
2. common error messages have localized variants
3. new copy can ship in two languages in one release cycle

Next step: Resource navigator.