Documentation refactor · journey-led state
Five clear ways into HyperFrames.
The documentation now begins with the situation a person is in: understand the product, make a first video, choose a workflow, edit a project, or recover from a problem.
250
navigated pages
5
canonical P0 journeys
4
top-level tabs
3
old routes redirected
What changed
Understand
One sendable explanation with a finished video, product loop, examples, and a clear
next step.
Complete
First video
A material-first route from a useful request through creative approval, Studio
review, and export.
Complete
Workflows
An outcome-led chooser plus consistent product, explainer, PR, recut, motion, music,
slideshow, and custom-video guides.
Complete
Studio
A task-led route for understanding an existing project, making the right kind of
change, checking it, and exporting safely.
Complete
Recovery
A symptom-first help entrance with small fixes, useful diagnostics, detailed
troubleshooting, and human escalation.
Complete
Removed or corrected
- False claims that Studio had no timeline or split workflow.
- Empty Weekly Updates and overlapping Showcase, Launch Videos, design, and troubleshooting pages.
- Repository-shaped top navigation and buried Studio user instructions.
- Rigid internal pipeline guidance presented as a requirement for every user.
- Duplicate Catalog titles and technical file tables dominating every item page.
- Internal telemetry specifications presented as a normal feedback guide.
- Duplicate Overview, Choose your path, Create with an agent, and Help entrances competing for the same jobs.
- Machine-facing Claude Design and Open Design specifications cluttering the human creation journey.
Post-release measurement
- Review real Mintlify search terms and no-result queries after deployment.
- Use page and search analytics to decide which specialized guides should be merged later.
- Refresh screenshots when visible Studio controls change.