Whiteboard explainer

Make the explainer a great teacher would draw: a voice explains and the board grows with it, so the viewer watches the idea being built and remembers it.

The drawing is the explanation: each mark is drawn as the words that name it are spoken. A finished picture that fades or slides in is not a whiteboard explainer.

What has to be true

• Drawn as it is said. Each mark starts when the voice reaches it and is done before the next idea. Check it in the frames against the voice's word times, and report how close it is.
• True to the source. Every fact, number, term and example as the person's document has it. What you add is your own sentence, never a new fact; what you correct, you say.
• Words on the board spelled right, and readable at the size it will be watched.
• It holds up next to the best explainers you know, its drawings made for this subject. Watch the whole film as a viewer would, and keep refining until it does.
• It stays editable: the person can change the script, or put their own voice in its place, and the drawing still lands on the words.

What you have

A voice from npx openfilm get tts, with a WebVTT beside it that times every word; the person's own recording gets the same from get asr. Anything you can draw and move with: the web platform and any library on it, renderers whose output becomes a clip, any font whose license allows it, images from get, your own built-in tools, and services the person has keys for. OpenFilm's own rules still hold: the picture at t depends on t alone, a page has no sound, and what you render elsewhere enters as a clip under assets/ with the script that made it. Ask before downloading anything large onto the person's computer.

With the person