Guide

Locale files

One markdown file per locale, locale-specific bindings, and what to avoid.

The library does not own template files. Hosts pick one markdown file per locale (en/, es/).

Bind only the locale key the file owns

  • English file: {{ data.sheet.tradeName.en }}
  • Spanish file: {{ data.sheet.tradeName.es }}

Do not write || locale fallbacks. A missing value renders empty.

Write labels in the locale file

Do not use ::kv. Write labels in the locale file with GFM tables, ::if, and ::for.

Use ::include only for a stored markdown string.

Do not use [meta.locale]

Locale selection belongs in the host — which file you load — not in document metadata.

This pattern keeps one source of truth per language and avoids silent fallback to the wrong locale in print output.
Copyright © 2026