Translatable Theme Settings and Custom Attributes
Multilingual sites can now store a separate value per language for theme settings and custom attributes, with untranslated values falling back to the default language.
A bilingual site needs its header, footer, and the custom details on each record to read correctly in every language, not only its pages. Theme settings and custom attributes can now hold a separate value per language, so a Welsh visitor sees a Welsh footer and a Welsh attribute value without a duplicate attribute for each language. Existing values are carried into your default language, so nothing needs re-entering.
Translate only what needs it
Translation is opt-in. Custom attributes with text, textarea, rich text, or link values are switched on per attribute, and attributes you leave alone keep one shared value across every language. Theme settings are switched on in the theme's schema, per setting or for a whole group, so a theme developer decides which settings editors can translate.
Untranslated values fall back
A value with no translation shows the default language's value on the site, and later edits to the default language keep flowing through until a translation is added. In the admin, an untranslated text field shows the default language's value as a placeholder, so an empty field reads as inherited rather than missing.