Documentation is the other half of a tutorial
Some people watch, some skim, and search engines index the words. Producing a video and a written guide separately means writing the same walkthrough twice. Capture already understands your tutorial well enough to clean up its voiceover, so the written version comes from the same work.
How Generate guide works
- Edit the tutorial as usual. Cuts and trims carry through to the guide.
- Click Generate guide in the editor. If the project has no transcript yet, Capture transcribes it first.
- Capture writes the guide from the transcript, preferring your optimized voiceover, and your clicks: a title, an introduction and numbered steps.
- Each step gets a screenshot from the recording at the moment you clicked, plus a link to jump to that moment in the video.
Change the edit later and the guide is flagged as stale. Regenerate it to bring it back in line.
How to write software documentation when you would rather demonstrate it
Ask anyone who maintains a help centre what makes documentation slow, and it is never the typing. It is deciding the order of the steps, remembering the prerequisite you skip automatically, and describing a screen from memory precisely enough for a stranger to follow.
Demonstrating the task solves all three. You perform the steps in the right order because the product makes you, the prerequisite appears because you actually do it, and the screen is described accurately because the recording is the screen. Then you edit a draft instead of facing a blank page.
Good documentation still needs a human deciding what matters. It just does not need one transcribing their own clicks.
Where this sits in Braiv Capture
Guides are a long-tail capability of Braiv Capture, built on voiceover optimization. Guides are written in the tutorial’s source language. For written guides from videos already on YouTube, see YouTube video to support article.
