docs: add canonical pipeline guide (#937)#943
Merged
miguel-heygen merged 1 commit intoMay 18, 2026
Conversation
Move the 7-step production pipeline (Capture → Design → Script → Storyboard → VO + Timing → Build → Validate) into its own dedicated guide so it serves any Hyperframes project, not just website-to-video. Expand each step with file contents, project layout, gates, and iteration patterns. Reference the new page from website-to-video, quickstart, prompting, and launch-videos.
miguel-heygen
approved these changes
May 18, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #937.
What
Adds
docs/guides/pipeline.mdx-- a dedicated guide for the 7-stepproduction pipeline (Capture → Design → Script → Storyboard → VO +
Timing → Build → Validate). Cross-references it from
website-to-video,quickstart,prompting, andlaunch-videos.Why
Previously the pipeline was documented as a small table inside the
website-to-video guide. That under-sold it: The structure (and the
DESIGN.md/SCRIPT.md/STORYBOARD.mdartifacts) is useful forany multi-beat Hyperframes project, not just website captures, and
it's a natural orientation read for anyone learning the framework.
How
what the gate is for moving on, and how to iterate without re-running
the whole pipeline. Includes a project-layout diagram.
docs.json. It'sorientation for the rest of the Guides, followed by
website-to-video(the headline use case) and then the technique-specific guides.
website-to-videokeeps a brief overview table and links to the newguide; deeper detail no longer duplicated.
STORYBOARD.md/DESIGN.mdwere alreadyreferenced (
launch-videos) or where the/website-to-hyperframesskill is named (
prompting).Test plan
mintlify dev: new page renders, all cross-links resolve, navorder matches the intended
pipeline → website-to-video → ….website-to-videopage still reads coherently withthe trimmed pipeline section.