Builds, notes & transitions

Reveal content step by step, attach speaker notes, and animate between slides.


Build steps

End a list item or block with >>> to reveal it one step at a time. Steps number themselves in document order. Give two lines the same step to reveal them together. In the PDF, all builds are shown, because the print captures a settled frame.

## Why a new language
- PowerPoint is bulky XML       >>>
- Markdown is what LLMs write best  >>>
- One header defines the whole look >>>

In the web deck, press the arrow keys or space to move through builds and slides.

Speaker notes

A line that starts with ???, up to the next blank line, is a speaker note. It shows in the web presenter overlay. Press n to see it. The audience and the PDF never see it.

:: title ::
slaide
??? Open warm. The whole pitch: plain text in, beautiful deck out.

Transitions

Set transition: in a slide’s frontmatter to control how it animates in:

none · fade · slide-left · slide-right · slide-up · slide-down · zoom · morph

Use a cascading ~transition: in headmatter to set one default for the whole deck.

Morph

Give an element an id with {#id}. Put an element with the same id on the next slide. With transition: morph, the engine animates one into the other. This is great for a diagram that grows, or a title that slides into a corner.

layout: image-right
---
:: image ::
![Pipeline](pipeline.svg){#hero}
---
layout: image-left
transition: morph
---
:: image ::
![Pipeline](pipeline.svg){#hero}

The PDF captures settled frames. So a morph just ends on its final state in print. Nothing depends on catching it mid-animation.