Regional settings
If your project defines regional variants - languages, currencies, or anything else set up in your metadata configuration - a template that reads metadata can render one design per variant. The same banner then comes out in English with pounds and in French with euros, from one template.
This is the same mechanism the DAM uses in Regional settings on an asset, applied while a template renders.
What makes a template localized
Nothing beyond a variable that reads localized metadata. If a text placeholder uses the Asset metadata source and the field it points at belongs to a regional-variants group, the template is localized and the control becomes active.
There is no separate setting to switch on. See Variables for how to bind a variable to a metadata field.
Choosing a variant while designing
The Regional settings control sits in the editor header, marked with a globe. Open it and you get one entry per group your project defines - languages and currency are the usual pair, though a project can name and group its variants however it likes. Pick one variant per group and the canvas re-renders with those values.
Use it to check the design, not just the wording: translations change length, and a headline that fits in English may need a smaller size or a taller box in German.
The control is always visible, so its absence never leaves you guessing. When the template has nothing to localize it appears grayed out with a tooltip explaining why. Groups that offer only one variant are left out, since there is nothing to choose.
Choosing a variant for a variation
The same control appears in the variation builder. Choosing a variant there updates the preview and the metadata-driven fields, and the choice is stored with the variation when you save it - so a variation is a specific language and currency, not just a set of values.
That is how you produce a set of localized outputs: one variation per market, each with its own regional selection, all from one template.
When a variant has no value
A localized metadata field holds one value per variant. The variable renders the value for the variant you selected, and nothing else: if that field has no value for the selected variant, or your selection covers none of the groups it belongs to, the variable falls back to its default value rather than borrowing another variant's text.
That is worth knowing when a design looks right in one language and shows placeholder wording in another - the gap is in the asset's metadata, not in the template.
What changes and what does not
Regional settings change the values pulled from metadata. They do not change the design: layouts, layers, fonts and positions are the same for every variant. Anything typed directly into a text layer is also unaffected, because there is no metadata behind it to localize.
Where to go next
Variables to bind values to metadata.
Variations to save one output per market.
Last updated