Locales
Booking pages show in Danish or English, as the customer chooses. Your theme's own strings live in locales/da.json and locales/en.json; Truly's components and the drops come in the page's language already.
Files
Both files are required. Each is a JSON object of plain strings, flat or nested; keys are lowercase letters, digits, - and _, at most 64 characters:
{
"services": { "title": "Vælg behandling" },
"footer_note": "Vi glæder os til at se dig"
}
No HTML in strings: they are printed as text.
Using strings
<h1>{{ 'services.title' | t }}</h1>
t takes the dotted path of a key. A key missing from the page's language falls back to Danish. A key missing from both fails the page.
Danish first
A key in da.json that en.json lacks is a warning in the check report (missing_english_key), not an error: the version still uploads, and English pages show the Danish string. Add the English strings before you publish if English customers matter to the tenant.
Drops in the page's language
Drop values that are words (a day's name, a menu link's label, a plan's credits) are already in the page's language, so print them as they are. The drops reference says which are.