foliolisted

# folio Print-ready documents from HTML, using one shared design system. Install once: `pipx install "folio-press[all]"` — then `folio` is on PATH. ## Why this exists Documents drift. Ask an agent for a PDF twice and you get two different stylesheets. folio fixes the design system in *files* — a stylesheet, a chart theme, print page furniture — so every document comes out consistent instead of being re-improvised. Markdown is not the answer here: it has about eight visual elements, and a document that looks designed needs a cover composition, running headers, numbered figures, metric tiles, callouts with tone, status pills, and a contents page whose numbers are real. Author in HTML with folio's classes. ## Workflow ```bash folio doctor # FIRST RUN ON A NEW MACHINE — what's missing folio templates # the document types, and the theme each pairs with folio themes # the four design directions folio init --template invoice # scaffold that type here (default: report) folio build document.html --check # render, then measure the layout folio check document.html # measure without rebuilding folio components # the component vocabulary — READ FIRST folio gotchas # silent renderer failure modes folio imagery # before adding any non-chart image ``` `folio build` runs a sibling `charts.py` first, injects the stylesheet, then renders. The