We’ve long offered an option to mark parameters and fields as “localizable”. However, this feature required a value for each locale and forced each instance of the field or parameter to be fully localized (or never to be).

Customers told us they wanted more flexibility, like overriding localization on a per-instance basis. For example, they wanted to use a single dynamic token to supply localized data, rather than repeating that same token for each locale.

Now parameters and fields marked as "Localizable" may be localized.

Architects can set a default, but editors can override this setting in Canvas for each component or entry instance. Fields and parameters that are not localizable will continue to not have locale-specific values. Existing fields and parameters marked as localizable will be set to “localized”.

Additionally we are introducing a new "Locale values" drawer that provides an overview of all localized values of a property without having to switch locales.

With this feature, along with other recent and upcoming localization enhancements, editors now have more control to avoid tedious repetition when managing localized entries and compositions.

Learn more about how to manage locale-specific values in our localization guide.