Skip to main content
Translatable content allows localized values to be associated with a record. The presence of language configuration does not mean every entity or field is translatable.

Model concepts

A translatable implementation commonly has a base entity plus locale-specific values. Confirm the exact relation, default locale, locale identifier, and fallback strategy from the v6 entities and translation middleware.

Developer guidance

  • Preserve stable record IDs across locales.
  • Define behavior when a translation is missing or empty.
  • Validate that requested locales are enabled.
  • Keep business identifiers and numeric values consistent unless the domain explicitly localizes them.
  • Ensure search, sorting, and filtering use the intended locale.
  • Avoid overwriting another locale when updating one translation.

Verification

Inspect translation middleware, entity relations, services, migrations, and API tests. Document the supported entity/field matrix and request locale selection only after source verification.