mirror of
https://github.com/heygen-com/hyperframes.git
synced 2026-09-11 23:00:03 +00:00
ukimsanov
6fe5b4f82a
Adds the pages the rebuilt navigation is organised around, and moves the sidebar onto that structure. Every entry points at a file that exists after this commit; nothing is rewritten or removed yet, and no redirect is claimed yet. - Studio (13 pages) — the editor had no section of its own - One guide per creation workflow, matching the shipped agent skills - Section hubs: Concepts, Catalog, Developers, Deploy, Workflows, Help, Go further, Product updates, 30 Days of HyperFrames Pages a later commit retires drop out of the sidebar here but still exist and still resolve, so the site stays navigable at this commit. Incidentally fixes a link to /concepts from the Lambda migration guide that is broken on main today — the destination did not exist.
71 lines
2.7 KiB
Plaintext
71 lines
2.7 KiB
Plaintext
---
|
|
title: "Choose how to create"
|
|
sidebarTitle: "Choose how to create"
|
|
description: "Choose between a local HyperFrames project, hosted chat, a design-first handoff, or a HeyGen-generated video."
|
|
---
|
|
|
|
## I want an editable project on my computer
|
|
|
|
Use a coding agent with the HyperFrames skills. The agent writes an ordinary
|
|
HTML project that you can revise with the agent, open in Studio, inspect in
|
|
source, render locally, or automate later.
|
|
|
|
This is the default path for a video that will keep changing.
|
|
|
|
```text
|
|
Using /hyperframes, make a 10-second product intro for https://example.com.
|
|
```
|
|
|
|
<Card title="Make your first local video" icon="play" href="/quickstart" horizontal arrow>
|
|
Install the skills and create the first editable version.
|
|
</Card>
|
|
|
|
## I want to create inside an AI chat
|
|
|
|
Use the hosted HyperFrames MCP connector. It creates and renders through your
|
|
HeyGen account without a local HyperFrames setup.
|
|
|
|
Choose this when convenience matters more than owning the complete project
|
|
folder. Rendering and account access are hosted; local Studio, source editing,
|
|
self-hosting, and precise debugging belong to the local path.
|
|
|
|
[Connect HyperFrames to an AI chat →](/guides/mcp)
|
|
|
|
## I want to establish the visual direction first
|
|
|
|
Start in Figma, Claude Design, or Open Design when brand, layout, and scene
|
|
direction are the unresolved part. Then hand the project to a coding agent for
|
|
motion refinement, media, validation, and rendering.
|
|
|
|
The design tool supplies a first draft, not a substitute for watching and
|
|
checking the finished movement.
|
|
|
|
[Bring a design into a project →](/guides/design-tools)
|
|
|
|
## I want to create inside HeyGen
|
|
|
|
Use HeyGen Video Agent when you want a hosted prompt-native workflow that
|
|
assembles the script, visuals, narration, avatar, and motion for you. HyperFrames
|
|
can power its HTML motion graphics, but the delivery surface is different: the
|
|
local path gives you the project folder, source, Studio, and CLI; Video Agent
|
|
keeps generation and revision inside HeyGen.
|
|
|
|
[Learn how HeyGen Video Agent works →](https://help.heygen.com/en/articles/12402907-how-to-get-started-with-video-agent)
|
|
|
|
If a generated person is only one layer in a locally editable film, [add the
|
|
presenter as media inside a HyperFrames project](/guides/avatar-presenter).
|
|
HeyGen generation can use an account allowance or credits; local HyperFrames
|
|
rendering does not.
|
|
|
|
## If you are unsure
|
|
|
|
Start with the local path. It preserves the most options because the project
|
|
stays editable. Use the [developer journey](/developers) instead when your goal
|
|
is an application or automated pipeline rather than one video.
|
|
|
|
## Related topics
|
|
|
|
- [Make a first local video](/quickstart)
|
|
- [Create through a hosted AI chat](/guides/mcp)
|
|
- [Bring a design into a HyperFrames project](/guides/design-tools)
|