Skip to content

Write HTML. Render video. Built for agents.

docs: rename the Workflows nav group to Make a video and drop retired workflow steps (#5655)

WaterrrForeverc4edac305621
diff --git a/docs/docs.json b/docs/docs.json
index 69ae1285c8..61d0848000 100644
--- a/docs/docs.json
+++ b/docs/docs.json
@@ -158,7 +158,7 @@
]
},
{
- "group": "Workflows",
+ "group": "Make a video",
"pages": [
"workflows",
"guides/product-launch-video",
diff --git a/docs/guides/captions-and-recuts.mdx b/docs/guides/captions-and-recuts.mdx
index 8e5e3fa51a..b1e11c31f5 100644
--- a/docs/guides/captions-and-recuts.mdx
+++ b/docs/guides/captions-and-recuts.mdx
@@ -50,7 +50,7 @@ If you need to remove pauses, choose different moments, or reorder the speech, m
## Before it builds
-Confirm:
+Settle these in the request, or ask the agent to propose them first:
- **Captions:** the intended format and any names or terms the transcript may miss. HyperFrames can recommend a visual treatment after it sees the clip.
- **Designed overlays:** the format, layout, visual style, and how often a title, quote, statistic, or side panel should appear.
diff --git a/docs/guides/faceless-explainer.mdx b/docs/guides/faceless-explainer.mdx
index 198d916f21..98a248071a 100644
--- a/docs/guides/faceless-explainer.mdx
+++ b/docs/guides/faceless-explainer.mdx
@@ -27,9 +27,9 @@ Using /hyperframes, turn these notes into a short visual explainer for a
general audience: [paste notes]
```
-The agent proposes the teaching angle and asks about information that must stay
-exact. A topic alone is enough to begin; a script is useful only when its words
-are already approved.
+Say which facts or wording must stay exact, and ask the agent to propose the
+teaching angle first if you want to choose it. A topic alone is enough to begin;
+a script is useful only when its words are already approved.
## How should the idea land?
diff --git a/docs/guides/general-video.mdx b/docs/guides/general-video.mdx
index cd621df178..64d5d0efeb 100644
--- a/docs/guides/general-video.mdx
+++ b/docs/guides/general-video.mdx
@@ -26,12 +26,14 @@ Using /hyperframes, make a one-minute recruiting film from the interview clips
and office footage in assets. Keep the employees' own words central.
```
-The agent proposes a treatment and confirms the important intent before the
-build. Use this path when choosing the story together matters more than starting
-from one source.
+Ask the agent to propose a treatment first when you want to agree on it before
+the build. Use this path when choosing the story together matters more than
+starting from one source.
## How should the agent work with you?
+Say which of these you want in the request:
+
- **Build it for me** — let the agent make the creative decisions and return a complete first preview.
- **Review the story first** — approve the storyboard and rough layouts before detailed production.
- **Co-direct it** — shape the story, visual system, motion, transitions, audio, opening, and ending with the agent.
diff --git a/docs/guides/motion-graphics.mdx b/docs/guides/motion-graphics.mdx
index 7fe68a333f..0017b10ed8 100644
--- a/docs/guides/motion-graphics.mdx
+++ b/docs/guides/motion-graphics.mdx
@@ -6,7 +6,7 @@ description: "Make a short, motion-led title, statistic, chart, logo sting, or o
import { DocsVideo } from "/snippets/docs-video.jsx";
-Use Motion Graphics for one short, design-led idea—usually under ten seconds—where the movement carries the message.
+Make a motion graphic for one short, design-led idea—usually under ten seconds—where the movement carries the message.
<DocsVideo
@@ -27,9 +27,9 @@ Using /hyperframes, make a six-second motion graphic that counts from zero to
10,000 and lands on “Thank you.” No narration.
```
-The agent proposes the visual treatment and confirms the output when it could
-be either a finished video or a transparent overlay. Exact beat timings are
-optional unless a specific moment must land precisely.
+Say whether you want a finished video or a transparent overlay when it could
+be either. Exact beat timings are optional unless a specific moment must land
+precisely.
## What are you animating?
diff --git a/docs/guides/pr-to-video.mdx b/docs/guides/pr-to-video.mdx
index e6b26082e0..60d2231dd3 100644
--- a/docs/guides/pr-to-video.mdx
+++ b/docs/guides/pr-to-video.mdx
@@ -25,8 +25,8 @@ Using /hyperframes, explain https://github.com/owner/repo/pull/123 to product
and engineering teammates.
```
-The agent reads the actual pull request, proposes the angle, and confirms its
-release state before presenting a proposed change as shipped behavior.
+The agent reads the actual pull request and checks its release state, so a
+proposed change is not presented as shipped behavior.
## Who needs to understand it?
@@ -38,7 +38,7 @@ The same pull request needs a different story for users, contributors, or a soci
## Before it builds
-Confirm:
+Settle these in the request, or ask the agent to propose them first:
- the intended pull request and audience;
- whether the angle is a changelog, feature reveal, fix, or refactor;
diff --git a/docs/guides/product-launch-video.mdx b/docs/guides/product-launch-video.mdx
index e188030b21..d9f2fbd586 100644
--- a/docs/guides/product-launch-video.mdx
+++ b/docs/guides/product-launch-video.mdx
@@ -26,9 +26,10 @@ Give the agent the real product URL and the result you want:
Using /hyperframes, make a 30-second launch video for https://example.com.
```
-The agent inspects the product, proposes a direction, and confirms anything
-important that the request did not settle. Add an audience, required claim, or
-final action when one must be exact; you do not need to specify every scene.
+The agent captures the product and builds from what is actually there. Add an
+audience, required claim, or final action when one must be exact; you do not
+need to specify every scene. Ask for a storyboard first when you want to approve
+the shots before it animates.
## What should the video do?