What the recorder needs
The magenta cover that hides the page until t=0 is the recorder’s, so a page needs no
cover of its own. How it works explains
what the cover is for.
What the screenshot tool needs
decktalk shots opens the page with no query and reads window.__decktalk.catalog, a
list of { scene, name, steps } objects, and then opens ?step=ID for each step id. A
page that has no catalog is skipped with a warning. Frame mode, shots --section N --at S,
opens the page as the recorder does and reads window.__decktalk.fired for the log.
A minimal page
This page honors the whole contract in about forty lines. It has one scene with one step, and each cue reveals the element with the matchingdata-cue.
deck/plain.html
page = "deck/plain.html" and scene = 1, and cue 1.1a
and 1.1b in cues.json. The page has no autoplay timing, so a browser preview with
?scene=1 fires nothing until beats are given, and ?step=1.1 shows everything.
What the runtime adds
The runtime also gives a page an index of scenes and steps, autoplay fromhold and
data-at, the reveal effects, count-ups, typewriting, KaTeX typesetting with a wait for
the library, a camera push, and the warning list. The runtime reference
lists all of it, and a page by hand can grow any of it as needed.