Hermes Wiki
opportunities/2026-08-09-incremental-tech-explainer-video-workflow

Opportunities: Wiki Knowledge Applicable to Tech Explainer Video Workflow — Incremental Pass, 2026-08-09

Scope: CoursesDocs/content-as-infrastructure-and-removing-setup-friction.md, CoursesDocs/course-platform-analysis-part2-kodekloud-nana.md, CoursesDocs/course-platform-competitive-analysis.md, and CoursesDocs/top_15_tips.md (all substantially edited this window) checked against Projects/tech-explainer-video-workflow.md, the only Projects/ file describing the actual video/content production pipeline these CoursesDocs analyses are about.

The CoursesDocs analyses are strategy for a pipeline that already exists as a Projects/ file — but neither currently references the other

tech-explainer-video-workflow.md documents a concrete, already-built production pipeline (script → Eraser diagrams → OBS/Figma → DaVinci Resolve edit) explicitly designed to reuse the same footage across YouTube, Instagram, and unlisted course lessons. content-as-infrastructure-and-removing-setup-friction.md's Example 3 independently arrives at almost the identical idea from the strategy side — "every substantial blog post gets a short companion video where you build/demo the thing on screen... re-performing material you already wrote and understand cold" — without citing the production workflow that would actually execute it. Right now the "why" (content-as-infrastructure's funnel argument) and the "how" (tech-explainer-video-workflow's toolchain) live in different folders with no cross-link, even though they're describing the same pipeline from opposite ends.

top_15_tips.md's environment-setup-friction tip (#9) already has a matching skill draft — the video workflow project is where "record the setup process" (its own tip #5) should land

The content-as-infrastructure... note's Example 5 under setup-friction — "record a 3-minute 'here's exactly what a working setup looks like' video, separate from lesson content" — is a specific, small deliverable that fits directly into the existing tech-explainer-video-workflow.md toolchain (OBS screen capture, no A-roll/editing needed for this format specifically) rather than requiring new tooling. The corresponding skill draft, reduce-course-setup-friction (unresolved), already lists this as step 6 but doesn't reference the video-production project as the mechanism for producing it — worth linking so the skill draft points at concrete tooling instead of a generic "record a video" instruction.

Hermes Wiki