Quickstart
Install DeckTalk, build the scaffold, and add your voice. Ten minutes.
Your first deck
Write a section, cue it, and build a slide for it. The four files and how they refer to each other.
Reference card
Every file, command, variable, and exit code on one page. Written for agents and for people in a hurry.
Python API
Drive the pipeline from your own code.
Five words
The documentation uses five words with fixed meanings.
The same number
N names a section in the script, its [[section]] table, its key in
cues.json, and by default its scene in the page. Step ids and cue ids are strings that
the page and cues.json agree on, and the scaffold prefixes them with the scene number.
What DeckTalk is not
DeckTalk is not a video editor and never makes a screen recording of you. It is not an avatar generator. It does not time visuals by frame in code, as Remotion and Motion Canvas do. It is for the case where the timing should come from the words and the slides are yours.How the documentation is organized
- Get started installs the tool and walks through authoring one section.
- Concepts explains each input and the pipeline that turns them into a film.
- Reference lists every command, key, field, artifact, and Python name.
- Help covers the errors you can hit and the questions people ask before trying it.
Every page is also served as plain text for language models at
docs.decktalk.app/llms.txt and
llms-full.txt.