This is a native bento. Three cells, one shared grid, room for a clear argument.
<deck-bento>Use code, tables, diagrams and images. Pick the form that explains the point.
<deck-code>Switch layouts to give each idea its own rhythm.
<deck-split>A file you own
Readable tags. Ordinary CSS. Keep the source in Git and review exactly what changed.
This slide: deck-split + deck-code
A quick draft
Choose a layout. Add a claim and its evidence.
A deck for the room
Check the rendering. Review the story. Rehearse the transitions.
Native deck-versus gives each side equal space. You supply the distinction.
Advance to reveal the next step. The slide stays put.
Start with one sentence.
Show the source or the example.
Make the requested action explicit.
Palette → semantics → components
Set the type, surfaces, contrast and spacing. Then give individual components their own treatment.
This slide switches from night to paper.
01 / Brief
Name the audience, the decision and the sources. Install the authoring skills.
npx rikiki skills02 / Inspect
Check the rendered deck. Send the diagnostics back for revision.
npx rikiki check talk.html --json03 / Review
Render screenshots, inspect them and revise. Revise until each slide makes its point.
npx rikiki render talk.htmlBrowser inspection
Catch reported defects in the rendered deck. Inspect every slide and reveal state.
Editorial judgment
Read the evidence. Judge the hierarchy, pacing and visual composition.
Zero reported errors does not certify a persuasive or beautiful presentation.
Open this tour full screen to try the shortcuts. These are native presentation controls.
Keep the editable source
Present in the browser. Bundle offline HTML. Export a PDF for the audience.
Start with the setup guide below this deck.
Start a deck
Bundle a standalone file
Export a PDF