Producing the document
One command, the same document every time.
The build is deterministic and scriptable: the same source produces the same document, on your machine or in a pipeline. Templates are versioned separately from content, so a work can be told what changed in its template and adopt it without losing what it edited.
What comes out
Five formats, one source
Markdown and HTML always. EPUB, DOCX and PDF once pandoc is installed.
House layouts and per-work compile settings decide how each one
looks.
Written for technical work
Code included by reference from real files and line ranges, so a listing
cannot drift from the program. Callouts on code lines, admonitions, table
control, figures generated at build, an index and glossary from markup, and
maths in both the preview and the export.
Round trips to reviewers
Send a chapter out as DOCX with comments anchored to the right sentences,
and take it back with the reviewers' comments as threads you can apply, fix or
resolve.
Review that accumulates
Findings per thousand words tracked across reviews, so you can see whether
a manuscript is improving. Where two reviewers disagree, the disagreement is
shown rather than averaged away.
Deterministic style lint
The checkable rules run as rules and are reported separately from the
model's judgement, so you always know which kind of finding you are
reading.
Page counts that are real
Measured from the built PDF rather than estimated from word counts, with
per-chapter figures derived from what the build actually
produced.