Pages and Frontmatter
A page is a Markdown file under locales/<locale>/pages/ with a YAML frontmatter block on
top. Its canonical logical path starts with pages/; the redundant physical wrapper is not
part of the path. The body is regular Markdown: headings, lists, tables, task lists, fenced
code with syntax highlighting, strikethrough, and autolinked URLs.
---
title: Installation
status: draft
tags: [setup]
---
## Requirements
...
Translation state
The supported states are translated and fallback:
- Omitting
translationmeanstranslated, including in the default-locale tree. translation: translatedrequires the page file in the requested locale. If it is absent, Codocation reports an ERROR and does not substitute default-locale content.translation: fallbackis valid only in a non-default locale. It resolves the logical page from the default locale without copying it. A fallback marker in the default tree, or beside an existing requested-locale file, is an ERROR. A missing default source is a reader failure.- Omitting the page from a locale tree excludes it from that locale. There is no
translation: excludedstate orreasonfield.
Every resolved resource keeps requestedLocale, sourceLocale, logicalPath, and
physicalPath. Internal links from an English fallback page displayed in German retain the
requested locale and apply the target page's own translation state. Writes always target the
requested locale, never the fallback source.
Other frontmatter keys
title- the page name shown in navigation, the browser tab, and search results. Without it, the first#heading of the body is used.status- the publication state:todo,draft,review, orfinal. Anything other thanfinalkeeps the page out of the built site, its navigation, sitemap, and search. A page with nostatuscounts as final.tagsandcategories- lists rendered in the page's meta row; see Tags, Categories, and Labels.date- shown as the "Last modified" stamp; on blog posts it also orders the listing.seo-description- the meta description for this page (search engines and link previews).hidden: true- keeps the page out of the site search index while still publishing it. This is useful for pages reached by a direct link only.noindex: true- emits a robots noindex meta tag for this page.layout: full- a landing page: the body mixes prose with:::hero,:::features, and other full-width sections. See Landing Pages.
Canonical links
Relative Markdown links are normalized against one virtual logical root containing the four
allowed namespaces: pages/, images/, attachments/, and assets/. They are not resolved
against a physical locale directory.
See [Navigation](navigation.md) and [Project Structure](../creating/project-structure.md).

[Download](../../attachments/manual.pdf)
[Styles](../../assets/css/site.css)
Fragments and queries are preserved. A path that climbs above the virtual root, starts with an
unknown namespace, or uses an unsupported assets/ child is invalid. Missing images or
attachments are validation errors after the permitted source-aware lookup.
Drafts in practice
Set status: draft while a page is in progress: preview and validation remain available, but
builds, deploys, and PDF export skip the page. Flip to final (or remove the key) to publish.