Frontmatter reference
There is no config file. All configuration lives in the frontmatter at the top of the source file — the part between the two --- lines.
The reasoning: one source file = one output, so configuration travels with the document and copying the document copies its settings. A separate config file adds a place for "the document is here, its settings are there" to drift apart.
The fields it knows
Six of them. Anything else reports a DOC-102 warning listing this set — never silently ignored, because silent ignoring lets you believe a setting took effect.
spec
Its role is singular: marking "this is a pamphlet source file". The current compiler supports version 1.
A value higher than the compiler supports reports DOC-101 suggesting an upgrade. A non-integer reports DOC-103.
It no longer triggers multi-parser behaviour — one parser is maintained. See the compatibility promise on the install page.
title
Without it, the search order is: the first # heading in the document → the literal string pamphlet.
theme
The built-in themes are sorted by document type. See Built-in themes for what each looks like.
The --theme flag overrides this field — a one-off intent should beat the document's standing setting.
An unknown name reports DOC-106 and falls back to default, still producing output: a wrong theme only affects how it looks; the content is fine.
lang
Written into the output's <html lang="…">. Defaults to zh-CN.
It affects how screen readers pronounce text and how browsers break lines and spell-check; it changes no compiler behaviour.
toc
Shortest form:
Full form:
The ToC is purely static: a nested list of anchor links, zero JavaScript.
The # heading does not appear in it — that is the document's own title. A deep outside 1–6 reports DOC-103.
Why skipTabs defaults to true
Tab panels are semantically several views of one topic; in a table of contents they read as separate chapters.
But tab labels are real headings, for accessibility and deep linking, so they inevitably enter the document outline — which is why the ToC side needs this switch.
Which side position puts it on
The default is side: a sticky side menu, pure CSS, zero JavaScript. Below 60rem it falls back to the top of the document.
To keep the ToC inline at the start of the body, scrolling away with the page:
Anything other than those two values reports DOC-103 as an error — it does not silently fall back to the default, which would let you believe the value you wrote took effect.
engines
command only
The command path works today; http (a remote rendering service) is not built yet and earns a DOC-104 note.
The full shape is described in Adding a custom diagram engine.
Diagnostics point at the field
Frontmatter diagnostics point at the line of the offending field, not vaguely at the ---: