The flow replayed with sample data. Use ↻ to play it again.
Start from Japanese (ja) and add the markets and languages you need, such as English, Korean or Vietnamese. Switch locale and the same page renders in that language.
Each market has its own set of locales and dictionaries, rendering the same structure in-language without duplicating the page. Per-market dictionaries keep both UI copy and content phrased consistently.
Localization builds on the structured content model, so adding a market never means rebuilding pages. Combined with multi-site publishing, each market's site is delivered in the right language.
- Add as many markets and languages as you need
- Switch locale and the same page renders in-language
- Per-market dictionaries keep phrasing consistent
- One schema shared across every market
How it works
- 1Open a page and switch to the locale you want to edit.
- 2Enter the translations for that market in the same field structure.
- 3Check how each locale renders in the signed preview.
- 4After review and publish, the content is served per market and locale from the translations API.
FAQ
Which markets and languages are supported?
Currently Vietnam (vi, en), the Philippines (fil, en) and Indonesia (id, en).
Do we need a copy of each page per language?
No. One structure is rendered with per-locale values, so pages are localized without duplication.
How does a front-end fetch translations?
Call the public API's translations endpoint with the market and locale.