Skip to main content
View as Markdown

Documents

Every render produces a written guide as well as a video — the same steps, in text, from the same recording. Neither one is transcribed from the other, so they can't drift apart.

Why both​

Some people won't watch a video. Some can't — they're in an open-plan office, or they need to copy a value out of step four. A written guide is also what search engines and support agents can actually use.

Maintaining both by hand is where teams give up, which is why this is generated rather than asked of you.

Editing a document​

Documents open in their own editor. Edit them like any document — the text is yours to change.

Density​

Documents can be regenerated at a different level of detail: a terse checklist for people who know the product, a fuller walkthrough for people who don't. Same source, different density.

Regenerating​

If you change the video, regenerate the document to match. This is a deliberate step rather than an automatic one, so edits you've made to the text aren't silently overwritten.

Exporting​

Export a document to publish it in a wiki, a help centre, or anywhere else, independently of where the video goes.