Text in, PDF out
No dragging, no nudging, no alignment guides. Write the words, pick a layout, build.
Overview
You have been on the receiving end of slide decks where every slide is slightly different from the one before. The headline is in one font on page 4 and another on page 5. The accent blue drifts between two shades. A chart copied from a 2022 deck still says “FY22” in the corner. Nobody planned the drift — it happens because slide tools make every slide a blank canvas, and humans are humans.
Lattice is what you build when you want to stop that from happening. The author writes the deck as a plain Markdown file, picks one of the named layouts for each slide, and the engine assembles the deck against a shared palette. Every deck looks like it came from the same team — because, structurally, it did.
One palette, every deck
Brand colors live in one file. Change them once; every deck picks them up on the next build.
Themed diagrams
Mermaid flowcharts and more render in the deck’s palette automatically — no per-diagram styling.
Version control
A deck is text. A normal git diff shows what changed between
revisions, the way it does for code.
Accessible by default
Contrast is WCAG AA across every layout.
No service, no account
Runs on your laptop or in CI. Fully offline-capable. No telemetry. MIT-licensed.
Where to go next
Section titled “Where to go next”Get started
Install the toolchain and render your first deck in a few minutes.
Author decks
Learn the layout catalog and the authoring contract.
Component reference
Every layout, modifier, and substance contract — themable in all palettes.