From Wiki Page to Tutorial Video
Wiki pages can become tutorials when they have a clear beginner problem, a short sequence of steps, and visuals that demonstrate the workflow without exposing private data.
When this matters
This page is for operators who want Rocky to produce usable work without turning the system into a mystery box. Use it when you need a practical path, a clear verification step, and a boundary between suggestion and action.
The operating pattern
- Choose a narrow promise. One video should solve one setup or workflow problem.
- Write narration from the article. Use the wiki page as the factual spine, not a script dump.
- Create safe visuals. Replace personal paths, emails, tokens, account IDs, and private data.
- Render a title/thumbnail QA frame. Check spacing, capitalization, and avatar crop before rendering the batch.
- Publish with metadata. Title, description, tags, and links should connect back to the wiki page.
Pre-flight checklist
- One clear audience
- No private data in frames
- Readable title slide
- Audio stream verified
- Wiki backlink included
Common failure modes
- Trying to cover everything: Beginner tutorials work best when narrow.
- PII in screenshots: Demo environments need sanitized names and paths.
- Skipping thumbnail QA: Bad title slides make the whole channel look amateur.
Verification
A page is not done because it was drafted. Verify the source, run the workflow, inspect the output, and record what changed. If a step touches money, customers, accounts, permissions, or private data, keep it behind an explicit human approval gate.