2.2.3 Localization Setup — Translatable Fields

Localization is a core capability of the Praisma Hub CMS. Content types can be configured to support multi-language content in a structured and predictable way, without duplicating schemas or fragmenting data.

This section describes how translatable fields are defined and how localization is applied across content types.

Localization Model

Praisma Hub uses a field-level localization model:

Content types define which fields are translatable

Non-translatable fields remain shared across languages

Translations are linked through a single content identity

This model balances flexibility with structural clarity.

Translatable Fields

Fields marked as translatable:

Store language-specific values

Appear in the editor per active locale

Participate in language-aware validation and workflows

Examples include titles, body text, summaries, and labels.

Non-Translatable Fields

Some fields remain language-independent, such as:

Internal identifiers

Configuration flags

Structural relationships

Shared metadata

This prevents unnecessary duplication and ensures consistency across languages.

Editorial Workflow and Localization

Localization integrates with editorial workflows:

Draft and publish states are tracked per locale

Missing translations can be identified

Editors can work on languages independently

This supports phased rollouts and controlled publication.

Rendering and APIs

Localized content is resolved at runtime based on:

Active language context

Fallback rules

Availability of translations

APIs and front-end rendering layers receive correctly localized output without additional transformation.

Summary

The localization setup in Praisma Hub enables structured, scalable multi-language content management. By defining translatable fields at the schema level, the CMS ensures consistency, editorial clarity, and reliable localization across the platform.