Turn a document into slides, control the layout, and reveal diagrams step by step.

Slides: one heading, one slide

Any doc renders as a deck with chiltepin slides. Each # or ## heading starts a new slide and becomes its title. Everything until the next heading — prose and blocks — stays on that slide. (### and deeper stay in the slide body.)

# Why now
A sentence of context, then any blocks under this heading.

```drivers
items:
  - { title: Slow, body: "p95 hit 2.4s.", icon: clock, accent: amber }
```

# The fix
Next heading → next slide.

Keep each section focused on one idea. Preview the deck to check whether its text and diagrams fit comfortably on screen.

Layout

Slides lay themselves out: light slides center, full slides top-align, and a slide with substantial prose plus a diagram automatically goes side by side — message left, exhibit right. Diagrams render borderless on the stage, without the card frame pages use.

The text a deck needs

A block's lede supplies a supporting line under the slide title. Use a {source: …} heading marker for attribution in the footer. Two or more divider bands add a section tracker to the slide header.

These heading markers control layout and presentation. They are removed from the displayed title:

Marker	Effect
`## Title {top}`	Align content to the top
`## Title {center}`	Center content
`## Title {bottom}`	Align content to the bottom
`## Title {split}`	Place prose on the left and one visual on the right
`## Title {source: internal QA, Sep 2026}`	Add a source line to the footer and under the heading in page view
`## Title {nobuild}`	Show the whole diagram without step reveals

Good to know

The meta block becomes the cover slide. Every other slide gets a footer with the deck title and page number.
Long sections split automatically across slides, keeping their title.
chiltepin build renders both views of every doc — the page and a deck — linked by a Doc | Slides toggle. No extra command.

Presentation-style decks

Choose blocks to support the point of the slide:

Purpose	Block
Introduce a problem and proposed answer	`scqa`
Compare options with ratings	`harvey`
Compare base, upside, and downside assumptions	`scenarios`
Start a new section	`divider`
Highlight one metric	`bignumber`
Summarize decisions or next steps	`takeaways`
Show phases or a plan	`chevrons` or `roadmap`

Find their fields in the block reference. To save the deck, run chiltepin slides docs/plan.md -o deck.html. chiltepin pdf docs/plan.md exports the document as a PDF; it does not convert the saved HTML deck.

Diagrams build as you advance

A diagram with a natural order reveals one item at a time before the deck moves on. sequence follows its messages (and its alt / else frame markers), flow walks the graph from start, saga runs its steps and then its compensations, spans arrives bar by bar; state, steps, timeline and rollout follow document order.

→ / Space / PageDown reveal the next step, then advance the slide. ← walks back. The step just revealed takes the accent for that moment — the one presentation-time exception to the one-accent rule.

Nothing is hidden by the markup: without JavaScript, in print, and on the page, the diagram is whole. Each build is announced through an aria-live region ("Step 3 of 18"), and prefers-reduced-motion drops the fade.

Opt one slide out with a heading marker:

## Architecture at a glance {nobuild}

One look, no themes

Decks use the configured colorScheme: dark, light, or system. Print and PDF use the light scheme. See Configuration for the shared setting.

Slides & decks