Plan the locale
Each enabled locale has its own public URLs, navigation labels, page metadata and CMS readiness. A locale is not a client-side text toggle over one canonical URL.
- Choose the default locale and a clear fallback policy.
- Confirm that the selected fonts contain every required glyph.
- Decide which pages and CMS resources must be complete before that locale can publish.
Translation workflow
- Add the locale in Dashboard → Localization.
- Translate shared navigation, footer, reusable definitions and design-system messages.
- Translate page/component content and localized SEO title, description and social metadata.
- Use provider suggestions only as reviewable drafts; a human accepts the final text.
Publish and verify
Readiness reports missing required units and stale source translations. Publish only when the locale policy passes, then verify canonical and hreflang links, language switching and localized sitemap entries.
Test long strings and mixed content at mobile widths. A complete translation can still break layout or accessible names.