9 shots · about 1 min 32 s of finished video · lesson 3 of Recording tutorials & testing with the guides
Record as
Any staff login
Sign in at /demo on a demo-mode build
Screens
/help/production /help/[course]/[lesson]/script /demo
Length
1 min 32 s
narration at ~150 words/min + screen time
Status
Not yet recorded
Before recording
Set up the screen, record one shot per step while reading the voice-over, and keep the cut faithful to the guide so the chapters line up.
| # | Screen | Action (on screen) | Must be visible | Voice-over | ~s |
|---|---|---|---|---|---|
| 1 | /help/production | From Help → Recording plan, filter Not recorded, pick a lesson and click Open script. | The shot list with the persona, the screens, the estimated length and a status of Not yet recorded. | Start from the recording plan so two people never record the same lesson. | 9 |
| 2 | /help/[course]/[lesson]/script | Click Copy as Markdown and paste the script into your edit notes, or Print shot list for a paper copy. | A Markdown document with an intro, one table row per shot, callouts and an outro. | The Markdown copy keeps the voice-over lines next to the actions, which is what you read while recording. | 11 |
| 3 | /demo | Prepare the browser: window at 1920×1080, zoom 100 %, light theme, language English, sidebar open, no other tabs visible. Sign in at /demo as the persona the script names. Callout: Reset the lesson's ticks (Reset above the steps) and re-seed the demo school if a previous take changed the data. | The app looks exactly like the screenshots a new user will see. | Consistency across videos matters more than any single effect: same size, same theme, same school. | 10 |
| 4 | /demo | Record the intro first: show the lesson's first screen while reading the intro voice-over (the lesson summary). | A 5–10 second opening that states what the viewer will be able to do. | Tell them the outcome before the clicks. | 7 |
| 5 | /demo | Record one shot per row of the table: perform the action in the Action column, hold until what the Must be visible column describes is on screen, and read the Voice-over column. Pause two seconds between shots so cuts are easy. | A take per step; the ~s column is the target length, not a limit. | If a shot goes wrong, stop, undo in the app, and record that shot again; never skip a step or the chapters will not line up with the guide. | 16 |
| 6 | /demo | Where a row has a Callout, add it on screen as a short text box or highlight during that shot. | Tips appear exactly where the written guide shows a lightbulb. | Callouts carry the tips that the voice-over does not. | 8 |
| 7 | /demo | Record the outro reading the What you have now lines, then end on the finished screen. | The video closes on the result (a receipt, a published report card, a saved timetable). | End on the proof that it worked. | 7 |
| 8 | /demo | Edit: keep shots in the written order, cut dead time, add a title card with the lesson title and the course name, and keep the final file at 1080p. While editing, write down the start time of each shot in seconds. | A list like 1: 0, 2: 18, 3: 41, … — one entry per step. | Those start times become the chapters that let a viewer jump from any step in the guide straight to that part of the video. | 14 |
| 9 | /demo | Upload to YouTube with the title Unibandh · <Course> · <Lesson title>, put the lesson's intro text in the description, and add the chapter list to the description as 0:00 Step 1 – … lines. | A public or unlisted video with YouTube chapters. | Use the lesson title verbatim so the video and the written guide are easy to match. | 10 |
After the video is published
Add its YouTube id under video-record-a-lesson in src/lib/help/videos.ts, with a chapters map of step number → seconds. The lesson page then shows the video and a “Watch this step” link on every step. See the video production guide.