Dashboard · Data

Naming & locales

Use dotted keys grouped by set. Sets are organizational; the full key is what content references.

Key conventions

Do

  • site.phone, site.address, library.stats.count
  • Stable names that survive redesigns
  • Group related keys under one set prefix

Don’t

  • Don’t put locale codes inside the key — locales are a separate axis
  • Don’t use spaces or random IDs as keys
  • Don’t store secrets in any key

Sets

Sets such as site or library help the Data UI group variables and can align with sync groups for data sources. Creating a variable-set is organizational; references always use the full dotted key.

Locales

Content languages are managed under Settings → languages. Variable values can be locale-aware depending on how you author them in the Data UI — keep marketing copy per locale, keep shared facts (phone) consistent unless you intentionally diverge.