avodado
avodado docs
CLI

Render commands

Turn docs into styled HTML pages, PDFs, PowerPoint decks, or a full static site.

Rendered output is self-contained HTML — styles and SVG diagrams inlined, no runtime JavaScript. Six themes; see Slides & theming.

avo preview

Render one doc and open it in your browser.

avo preview docs/orders.md

avo html

Render one doc to a standalone HTML file.

avo html docs/orders.md -o orders.html
avo html docs/orders.md -p            # render to a temp file and open it

avo pdf

Render one doc to a PDF.

avo pdf docs/plan.md         # → plan.pdf   (-p opens it)

Chromium downloads automatically on first use (about 100 MB, once). To install it ahead of time: npx playwright install chromium.

avo pptx

Render one doc to a PowerPoint deck — the same slides avo slides produces, as a .pptx you can hand to anyone.

avo pptx docs/plan.md        # → plan.pptx  (-p opens it)
avo pptx docs/plan.md -e     # editable: native text, tables, and charts

By default every slide is a full-bleed image of the rendered slide, so the deck looks exactly like the browser version — fonts, diagrams, and theme included.

--editable (-e) builds the deck out of real PowerPoint objects instead: text boxes, tables, and charts your audience can edit in PowerPoint or Keynote. Diagrams have no PowerPoint equivalent, so those slides fall back to an image — a typical deck comes out mostly native with a handful of picture slides. Like avo pdf, both modes need Chromium (it downloads once).

avo build

Build a static site from all docs — an index page, sidebar navigation, cross-doc links, and a Doc | Slides toggle on every page.

avo build                    # → dist/    (--out <dir>)

The live demo on this site is exactly this: avo build run on this repo's own docs.

A live local site

Want to browse the built site while you edit? In avo studio, Site ↗ opens the same site avo build produces in a new tab — one click away, rebuilt on every save.