crossPresent — Feature Tour
Every block type the generator supports, in one deck. Open the source file side by side with this page — each slide shows what the Markdown looks like rendered.
The whole deck you are reading was generated from examples/demo.md with one command:
crosspresent build examples/demo.md
Text, badges and notes
The first paragraph of every slide is styled as an intro — slightly larger, capped at a readable line length. Use it to frame the slide.
Regular paragraphs follow. Inline markup: bold, italic, inline code, and links. Badges are double-bracket shorthand:
[[shipped|good]]renders shipped[[in review|warn]]renders in review[[broken|bad]]renders broken[[v2.1|info]]API design infra plain
Start the first line with a bold phrase and it becomes the note's label. Use these for the "here is the catch" moments — the thing you would say out loud while presenting the slide.
Bar and grouped bar
A chart is a fenced block tagged chart containing JSON. Single values array gives you one series; series gives you groups and an automatic legend.
Horizontal bars
hbar suits long labels — categories read left to right instead of being crushed under the axis. Add "colorful": true to cycle the palette per bar.
Lines and areas
line takes the same JSON as bar. Multi-series gets a legend; an area chart is a line with the region under it filled.
Pie and donut
pie and donut take one series. The legend carries values and percentages, so the slices stay clean.
Charts from data files
Instead of inline numbers, point a chart at a CSV (or JSON) file with "data". First row is the header, first column is the labels, every other column becomes a series. The chart below comes straight from data/weekly.csv — regenerate the CSV in CI and the deck stays current.
Stat tiles
A stats block is one line per tile: value | label | color. Colors: green, amber, red, blue, gray (or leave blank).
Tables
Standard pipe tables, with alignment markers in the separator row. Cells take the full inline syntax — badges included.
| ID | What it does | Status | Runtime |
|---|---|---|---|
| TP-01 | Default id=doi:… resolves | passing | 0.4 s |
| TN-03 | title alone should be rejected | xfail — Finding 2 | 0.3 s |
| S-03 | Unresolved envelope validates | skipped — Finding 7 | — |
Cards
A cards block splits on ### headings into a responsive grid. Column count is automatic (2 or 3) or forced with `cards 3 .
Black-box only
Assert on what the API outputs — status, headers, body, timing. Nothing about server internals.
Offline / live split
Live tests skip unless --run-live is passed, so CI without network access still has a gate that means something.
One HTTP client
Every test goes through one client — base URL, retries, pacing. Tests read as intent, not plumbing.
Columns
Put things side by side with a columns block. Separate columns with a line containing only |||; add a ratio like 3:2 to set their widths.
Why it matters
- Text and a chart on one slide, without HTML
- Each column is ordinary slide Markdown
- Collapses to one column on narrow screens
Code and pills
Fenced code with any other tag renders as a code block:
def resolve(doi: str) -> Response:
return client.get(params={"id": f"doi:{doi}", "redirect": "false"})
A pills block makes a row of link chips — good for closing slides:
That's every block.
Scaffold your own deck and start from a working file:
crosspresent new mydeck
crosspresent build mydeck.md --open --controls # arrow keys + F for fullscreen
crosspresent pdf mydeck.md # 16:9 PDF with -t deck