mirror of
https://github.com/heygen-com/hyperframes.git
synced 2026-11-15 13:58:20 +00:00
ukimsanov
b4648e0e5a
Product launch, colour grading, faceless explainer, captions and recuts, motion graphics, and voice and audio. Five of these led with a six-to-eight second teaser. A six-second clip on the page that teaches you to make explainers does not teach anything — it is a placeholder that looks like content. Colour grading, the most visual feature in the product, had no video at all. The new films are 34 to 41 seconds and each shows a RANGE rather than one look: four ways to tell the same idea with no footage; five caption treatments on one untouched clip; correction, presets, curves, selective colour, all four scopes and a LUT; narration with music ducking under it and effects on the beat. The launch film is built by running the workflow on huly.io for real, so the page that sells the workflow is showing its actual output. They share one visual system, measured from HyperFrames own light-theme launch films rather than invented: bone field, near-black type, coral accent, and the product always a dark panel inset on the light field. Every one carries audio at about -20 dB and is 1-2 MB. The old teasers are removed from the three pages where they became a duplicate. They stay in the workflow picker, which is where a six-second tile belongs. Guides with nothing to look at: 15 at the start of this work, 5 now.
73 lines
3.2 KiB
Plaintext
73 lines
3.2 KiB
Plaintext
---
|
|
title: "Create a faceless explainer"
|
|
sidebarTitle: "Faceless explainer"
|
|
description: "Turn notes, an article, or a difficult idea into a visual explanation without product footage."
|
|
---
|
|
|
|
import { DocsVideo } from "/snippets/docs-video.jsx";
|
|
|
|
Start from a topic, article, or notes. HyperFrames invents the typography, diagrams, abstract graphics, and data visualization that teach it.
|
|
|
|
|
|
<DocsVideo
|
|
title="One idea told four ways, with no footage to start from"
|
|
src="https://static.heygen.ai/hyperframes-oss/docs/images/showcase/faceless-explainer-demo-v1.mp4"
|
|
poster="https://static.heygen.ai/hyperframes-oss/docs/images/showcase/faceless-explainer-demo-v1.jpg"
|
|
/>
|
|
|
|
Kinetic type, an abstract graphic, a diagram, and a data-visualisation — all
|
|
invented from the text. There is no source video anywhere in this.
|
|
|
|
## Make the request
|
|
|
|
Attach or paste the source material:
|
|
|
|
```text
|
|
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.
|
|
|
|
## How should the idea land?
|
|
|
|
- **Understand one idea** — open with a useful question, then reveal the mechanism one layer at a time.
|
|
- **Follow a process** — keep one visual stage and show each step in the order the viewer needs it.
|
|
- **Remember three points** — make the ideas parallel, concrete, and visually distinct enough to recall later.
|
|
- **Learn through a story** — use one case to move from setup and tension to a general lesson.
|
|
|
|
If you supply an approved script, say whether HyperFrames may restructure it or
|
|
must keep every word.
|
|
|
|
Use a [product and website video](/guides/product-launch-video) when the real interface should provide the proof. Use [captions or designed overlays](/guides/captions-and-recuts) when existing footage should remain underneath.
|
|
|
|
## From information to understanding
|
|
|
|
HyperFrames does not turn each paragraph into a scene. It finds the teaching spine, removes asides, and builds a sequence around the one idea the viewer should retain.
|
|
|
|
The visuals share one coherent language and develop with the explanation. A diagram should reveal a mechanism; a chart should prove a claim; motion should show what changes.
|
|
|
|
## Review whether it teaches
|
|
|
|
- The opening creates a question, tension, or surprise.
|
|
- The main idea is clear by the second scene.
|
|
- Each body scene advances one mechanism, step, example, or implication.
|
|
- Numbers and factual claims match the source.
|
|
- The ending lands the sentence you wanted the viewer to remember.
|
|
|
|
Ask the agent when the teaching sequence or evidence must change. Use
|
|
[Storyboard](/studio/storyboard) to inspect the sequence directly, or Studio
|
|
for a precise visual, timing, or animation correction.
|
|
|
|
<Card title="Finish and share" icon="circle-check" href="/guides/export-and-share">
|
|
Check the final project, render through your preferred surface, and review the file.
|
|
</Card>
|
|
|
|
## Related topics
|
|
|
|
- [Prompt for explainers](/prompting/explainers)
|
|
- [Review the storyboard](/studio/storyboard)
|
|
- [Create a product video from real screens](/guides/product-launch-video)
|