Bilingual pages

Content is bilingual: a page is a pair of language-suffixed files side by side in the same directory, each publishing under its own language-aware URL.

content/docs/site-governance/content/example.en.md
content/docs/site-governance/content/example.fr.md

Identical base filenames link the two files as translations automatically. When the filenames differ, the same translationKey in both files links them instead.

Four rules keep the pair coherent:

• Not every page has a translation. A page may exist in one language only; check that the counterpart file exists before linking across languages.
• The French file may set slug: to give the translation a localized URL. The translation link survives because it rests on the filename or translationKey, not the URL.
• related: paths are language-agnostic. Each language site resolves them against its own pages, so the identical list goes in both the .en.md and .fr.md front matter — a list maintained in only one file leaves the other language rendering nothing. See cross-references.
• Code stays verbatim. Commands, paths, config keys, and shortcode examples are identical in both files; only the prose is translated.