ScribleSketch AI slide decks, from your notebook.
Slides aren't a separate file. They're a paginated view of your notebook — same blocks, same renderer, same theme tokens. Chop on H1, attach speaker notes, present from the workspace, export to PDF / PNG / GIF.
- LogisticsRC
- FinanceTM
- TeamIF
- LogisticsRC
- FinanceTM
- TeamIF
Slides are a view, not a file.
Each H1 in your notebook starts a new slide. Every block underneath travels with it — KPI strips, paragraphs, callouts, images. Override the chop point on any heading if you want.
Five weeks across logistics, finance, and the team. Each track has an owner and a known blocker.
- LogisticsRC · weekly
- FinanceTM · biweekly
- TeamIF · daily standup
Break on H2 instead of H1 for denser decks. Mark a heading as "no-break" to keep two ideas on one slide. The chop logic is just metadata — no rebuild needed.
What only you see.
Press P to present. The audience sees the slide. You see the slide, the next slide, your speaker notes, the build sequence, and a quiet timer. Plus keyboard control for builds.
Lead with the risk number — set it up first, then explain the cable-runs hold. Build in: open → on-track → risk. Pause on risk for the question.
- ✓Reveal headline
- ✓Show open KPI
- 03Show on-track KPI
- 04Show risk KPI · stay on this
- 05Cue to next slide
Six slides. One composition.
Slides aren't templates — they're emergent layouts the renderer picks based on what blocks are present. Heading + paragraph → title. KPI strip → KPI slide. Image hero → fullbleed.
- LogisticsRC · weekly
- FinanceTM · biweekly
- TeamIF · daily standup
Three tracks, one risk, no surprises. The cable runs are the single blocker on the operations side.
- 01Where Q2 stands
- 02Owners & cadence
- 03Cable-runs blocker
- 04Q&A
Need a custom layout? Drop a hero block, a card grid, a doodle — slides pick up whatever the section contains. The renderer never breaks.
One renderer. Every format.
What you see in the preview is what arrives in the file. PDF / PNG / GIF are all driven by the same CompositionRenderer running off-screen — same blocks, same theme tokens, same paper.
DOM-based render means fonts, paper grain, and accent colors survive end-to-end. No flatten-and-re-render losses.
All export formats