Text in, PDF out
No dragging, no nudging, no alignment guides. Write the words, pick a component, build.
Lattice turns a plain Markdown file into a boardroom-ready slide deck: you write the words, pick a named component per slide, and the engine sets every page in one shared palette. For the full story — what it is, who it’s for, and what it deliberately isn’t — start at What is Lattice? This page is the map.
Text in, PDF out
No dragging, no nudging, no alignment guides. Write the words, pick a component, build.
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 component.
No service, no account
Runs on your laptop or in CI. Fully offline-capable. No telemetry. Open source (AGPL-3.0).
What is Lattice?
The one-paragraph version, and who it’s for.
Principles
The convictions behind the engine — why a slide is four decisions, and why the colors live in one file.
Get started
Install the toolchain and render your first deck in a few minutes.
Author decks
Learn the component catalog and the authoring contract.
Themes & palettes
How palettes work, the ones that ship, and how to author your own.
Component reference
Every component, modifier, and substance contract — themable in all palettes.