Translations

What It Is

Jetstack includes a schema-translation subsystem for selected implementation objects and fields. It supports locale management, enabled locales, default locale, fallback chains, field translations, option translations, bulk editing, and AI-assisted suggestions.

Why It Matters

Translations affect:

  • type names
  • module labels
  • property labels
  • property options
  • enumeration values
  • search and display behavior for translatable implementation fields

In multilingual tenants, translation design becomes part of implementation architecture, not an afterthought.

Translation Scope

The translation system covers at least:

  • types
  • modules
  • properties
  • property options
  • enumeration values

Locale Model

The tenant can define:

  • available locales
  • enabled locales
  • a default locale
  • fallback locale relationships

Fallback chains matter because runtime rendering often resolves to the first available translation in the chain rather than only an exact locale match.

Editing Model

Jetstack supports:

  • locale management
  • field-level editing
  • bulk translation editing
  • AI suggestion workflows

This makes translation management an ongoing operational process rather than a one-time import.

Runtime Consequences

Translation behavior influences:

  • displayed labels
  • translated option lists
  • title-like filter behavior
  • search indexing and search results

Best Practices

  • define a clear default locale early
  • enable only the locales the tenant can realistically maintain
  • document which object fields are expected to be translated operationally
  • use AI suggestions as acceleration, not as unquestioned truth
Previous← Tenant SynchronizationNextUsers →