Localize content
Edit translatable and shared fields and check locale fallback.
Translatable fields can hold different values for each delivery locale. Shared fields always use the Backend’s default locale.
Access
You need backend.read, content.read, and content.update, with scope matching the Backend, Content type, and selected locale.
Edit a locale
- In entry details, use the Locale selector.
- Edit fields marked translatable. Shared fields continue to read and write the default locale.
- Select Save before choosing another locale.
- Switch locales and compare the saved values.
- Ask a developer to verify the public locale key in delivery when needed.
Publishing affects the whole entry, not one locale. The asset editor does not currently provide a locale selector.
Delivery checks the requested locale, configured fallbacks, the Backend default, then the nonlocalized value. An authored null or explicitly empty value stops fallback. The same locale choice applies to projection, filters, sorts, cursors, and nested references.