Skip to content
Alokai CMS

Localization

Alokai CMS supports per-locale page versions. Each locale gets its own independent version history and publish status.

Adding locales

Go to Settings → Locales and click New Locale. Enter:

  • Code — IETF language tag (e.g. en-US, de-DE, fr-FR)
  • Name — Display name (e.g. “English (US)”)
  • Default — Whether this is the fallback locale

Locales are per-environment. The main environment and a staging environment can have different locale sets.

Editing in a locale

Use the locale switcher in the page editor toolbar to switch between locales. When you switch locale, the canvas and property editor reload with that locale’s content.

If a locale has no content yet, the editor starts with an empty canvas.

Independent publish status

Each locale version is published independently:

  • Publish English without affecting German
  • Schedule French for a future date while English is already live
  • Archive a locale-specific version while keeping others active

Default locale

The default locale is used as a fallback when the delivery API is called without a locale parameter.

Delivery API with locales

Pass ?locale=<code> to the delivery API to request a specific locale:

GET /api/v1/pages/by-path/about?locale=de-DE

If the requested locale is not published, the API returns a 404.