From 22f96980a004ca981db328100baf6aa39ccce514 Mon Sep 17 00:00:00 2001 From: ukimsanov Date: Mon, 3 Aug 2026 15:41:35 -0700 Subject: [PATCH] docs: standardize video playback and add learning series --- docs/custom.css | 10 ++ docs/docs.json | 6 + docs/prompting/anatomy.mdx | 14 +- docs/prompting/capstone.mdx | 14 +- docs/prompting/captions-and-talking-heads.mdx | 9 +- docs/prompting/captions-catalog.mdx | 27 +++- docs/prompting/code-and-prs.mdx | 16 ++- docs/prompting/code-blocks.mdx | 38 ++++- docs/prompting/color-grading.mdx | 62 +++++++-- docs/prompting/data-and-maps.mdx | 38 ++++- docs/prompting/design-systems.mdx | 8 +- docs/prompting/editing-existing-videos.mdx | 14 +- docs/prompting/examples.mdx | 130 +++++++++++++++--- docs/prompting/explainers.mdx | 15 +- docs/prompting/generated-artwork.mdx | 20 ++- docs/prompting/media-and-audio.mdx | 14 +- docs/prompting/motion-graphics.mdx | 8 +- docs/prompting/motion.mdx | 74 ++++++++-- docs/prompting/music-and-slideshows.mdx | 14 +- docs/prompting/overlays-and-lower-thirds.mdx | 27 +++- docs/prompting/overview.mdx | 26 +++- docs/prompting/product-launch.mdx | 14 +- docs/prompting/recreating-references.mdx | 9 +- docs/prompting/rendering-and-output.mdx | 15 +- docs/prompting/runtimes-and-3d.mdx | 20 ++- docs/prompting/storyboards.mdx | 14 +- docs/prompting/transitions.mdx | 14 +- docs/prompting/variables-and-templating.mdx | 14 +- docs/prompting/vfx-and-liquid-glass.mdx | 32 ++++- docs/prompting/visual-specs.mdx | 20 ++- docs/prompting/vocabulary.mdx | 110 ++++++++++++--- docs/snippets/docs-video.jsx | 14 +- docs/thirty-days.mdx | 50 +++++++ docs/weekly-updates.mdx | 17 ++- 34 files changed, 796 insertions(+), 131 deletions(-) create mode 100644 docs/thirty-days.mdx diff --git a/docs/custom.css b/docs/custom.css index 0c9fcaf815..e7f20d6c5c 100644 --- a/docs/custom.css +++ b/docs/custom.css @@ -722,6 +722,16 @@ samp { width: 100%; } +.hf-docs-video-block[data-portrait="true"] { + width: min(100%, 18rem); + margin: 0.75rem auto 0; +} + +.hf-docs-video-block[data-portrait="true"] .hf-docs-video { + aspect-ratio: 9 / 16; + max-height: min(32rem, 68vh); +} + /* * Mintlify loads custom React snippets after the page shell. Reserve the * film's real shape so the unloaded component never flashes as a thin Frame diff --git a/docs/docs.json b/docs/docs.json index 2e408005cf..a12a6849ea 100644 --- a/docs/docs.json +++ b/docs/docs.json @@ -67,6 +67,12 @@ "product-updates" ] }, + { + "group": "30 Days of HyperFrames", + "pages": [ + "thirty-days" + ] + }, { "group": "Choose where to create", "pages": [ diff --git a/docs/prompting/anatomy.mdx b/docs/prompting/anatomy.mdx index 743a6a6c19..a5d77b11dd 100644 --- a/docs/prompting/anatomy.mdx +++ b/docs/prompting/anatomy.mdx @@ -3,6 +3,8 @@ title: Anatomy of a one-shot prompt description: "The six-part skeleton — route, spec, beats, copy, technique, negatives — that removes the decisions agents most often get wrong." --- +import { DocsVideo } from "/snippets/docs-video.jsx"; + Your Level 1 prompts worked because the workflow filled the gaps for you — the palette, the pacing, the structure. This is Level 2: the skeleton is how you take that control yourself. The [copy-paste examples](/prompting/examples) share one skeleton. Each part removes a decision agents most often get wrong on a first try: @@ -27,7 +29,11 @@ Assembled: > /motion-graphics Make an 8-second 1920x1080 video. Beat 1 (0-4s): dark macOS terminal types "npx skills add heygen-com/hyperframes" character by character, then hold on the blinking cursor. Beat 2 (4-5s): the terminal shatters into fragments. Beat 3 (5-8s): bold white kinetic text on black slams in word by word, snappy: "YOU JUST MADE THIS / WITH HYPERFRAMES." Adapt the `code-typing` and `vfx-shatter` registry blocks; hand-author the kinetic text. No narration, no image or media files. - + *Rendered from the prompt above, unedited.* @@ -101,7 +107,11 @@ This is the clause in the [full capstone prompt](/prompting/capstone#the-full-pr > **Mount (7–14s).** Traveling along the wire: it splits into three parallel track lanes; clip chips slide in along the direction of travel and seat onto the lanes on their spoken cues (audio track chip, video track chip, our protagonist chip among them). Small mono labels (`data-start`, `data-track-index`) tag themselves onto chips as the camera passes. The lanes merge back to one wire as the camera accelerates out. - + *That clause, rendered — the region cut from the finished film.* *Next: [The specification dial](/prompting/specification-dial) — how much of the skeleton to fill in, and when density stops being optional.* diff --git a/docs/prompting/capstone.mdx b/docs/prompting/capstone.mdx index b58c394457..221d90fc46 100644 --- a/docs/prompting/capstone.mdx +++ b/docs/prompting/capstone.mdx @@ -3,7 +3,13 @@ title: Capstone — every technique, one journey description: "One prompt, one continuous camera move, every technique in this guide — the viewer rides the timeline itself from typed markup to rendered MP4." --- - +import { DocsVideo } from "/snippets/docs-video.jsx"; + + *"The Timeline" — 1920x1080, ~62 seconds, one prompt, one unbroken camera move, unedited.* The prompt targeted roughly 60 seconds; the delivered render runs 1:02 because the final lockup holds for a two-second breath. @@ -111,7 +117,11 @@ HyperFrames scopes `data-composition-variables` **per composition file**, so the hyperframes render --variables '{"ground":"#0d1420","ink":"#c8ff3d"}' --strict-variables ``` - + *The same composition, navy/acid-green — the wire, ruler, chart, map, glass, and even the generated mural all follow the override.* The mural trick from the previous capstone carries over: the artwork is generated **palette-neutral** (grayscale) and duotoned live by CSS layers driven by the `ground`/`ink` variables, so even the raster re-skins. Keep color in CSS and shapes in the raster whenever a template frame needs to survive a re-skin. diff --git a/docs/prompting/captions-and-talking-heads.mdx b/docs/prompting/captions-and-talking-heads.mdx index f38a45fb25..dd3b983cae 100644 --- a/docs/prompting/captions-and-talking-heads.mdx +++ b/docs/prompting/captions-and-talking-heads.mdx @@ -3,6 +3,8 @@ title: Captions and talking-head footage description: "Two ways to dress an existing talking-head clip — readable captions or designed graphic overlays — both leaving the footage itself untouched." --- +import { DocsVideo } from "/snippets/docs-video.jsx"; + The first two rides built a video from nothing and the third built one from a diff. This one starts from footage you already have — a talking-head clip — and adds a layer on top without touching the shot itself. ## Your first win @@ -12,7 +14,12 @@ One prompt to [`/embedded-captions`](/prompting/overview), pointed at an existin Captions route by **identity**, not by mode. You pick one look from the catalog; the engine behind it is a lookup detail you never have to name. The default is a clean verbatim rail — `anchor` — with the occasional peak word composited behind the subject. > /embedded-captions Add captions to ./interview.mp4. Use the `anchor` identity — clean verbatim rail carrying the spoken words, readable lower-third. Promote the single hardest-hitting word to an embed behind the speaker; highlight one key word in each rail line. Keep the source aspect ratio. Footage stays untouched. - + + *Rendered from the prompt above on generated avatar footage, unedited — one earned embed behind the speaker, everything else on the rail.* diff --git a/docs/prompting/captions-catalog.mdx b/docs/prompting/captions-catalog.mdx index ba61fdf38f..ef86d9d9a8 100644 --- a/docs/prompting/captions-catalog.mdx +++ b/docs/prompting/captions-catalog.mdx @@ -3,6 +3,8 @@ title: Caption styles description: "Map caption tone to named caption components, and prompt per-word emphasis for composed videos." --- +import { DocsVideo } from "/snippets/docs-video.jsx"; + Your faceless explainer from Level 1 already asked for "embedded captions, keywords highlighted in the accent color" and got a sensible default. This chapter is the catalog behind that ask — the named components you can pin instead, by tone, so the highlight color and the animation are a decision, not a default. ## What caption styles do and when they trigger @@ -40,7 +42,12 @@ Three [Text Effects](/catalog/components/morph-text) components do one focused j > /faceless-explainer 30-second vertical explainer. Add [`caption-highlight`](/catalog/components/caption-highlight) captions, TikTok-style — the visible line stays up, one word highlighted at a time. - + *Rendered from the prompt above, unedited.* @@ -50,13 +57,21 @@ Three [Text Effects](/catalog/components/morph-text) components do one focused j > Hype captions with [`caption-kinetic-slam`](/catalog/components/caption-kinetic-slam): one full-screen word per beat, alternating slam-in direction. - + *Rendered from the prompt above with an authored 24-word line, unedited.* > Neon music-video captions using [`caption-neon-glow`](/catalog/components/caption-neon-glow). Make brand names larger with an accent color and highlight the numbers differently. - + *Rendered from the prompt above, unedited — the brand renders 1.4x in magenta, numbers in amber, distinct from the default cyan.* @@ -100,7 +115,11 @@ This is the clause in the [full capstone prompt](/prompting/capstone#the-full-pr > THEN they speak, and the main **keywords of their own line — derived from the clip's transcription — land word-synced as huge display text BEHIND the cutout**, each keyword slamming in on its spoken moment with the subject's silhouette occluding it (the two-layer text-behind-subject plate); style the keyword type by adapting a bold **catalog caption component** (`caption-kinetic-slam` or similar) at display scale. - + *That clause, rendered — the region cut from the finished film.* *Next: [When to generate artwork](/prompting/generated-artwork) — where hand-drawn HTML/CSS/SVG wins, and where a generated image beats it.* diff --git a/docs/prompting/code-and-prs.mdx b/docs/prompting/code-and-prs.mdx index 8a6120b4a9..8486012ffd 100644 --- a/docs/prompting/code-and-prs.mdx +++ b/docs/prompting/code-and-prs.mdx @@ -3,6 +3,8 @@ title: Code changes and PRs description: "What to say to turn a GitHub pull request into a code-change explainer — changelog, feature reveal, fix, or refactor walkthrough." --- +import { DocsVideo } from "/snippets/docs-video.jsx"; + Two rides in, both built from nothing yet on the page. This one starts from something that already exists and is already true — a merged PR — and turns the diff itself into the story. ## Your first win @@ -13,7 +15,11 @@ Verified, from the [examples](/prompting/examples) page — a 30-second feature > /pr-to-video Make a 30-second 1920x1080 feature-reveal video from [PR URL]. Lead with what users get, not the diff; show the key code change with the `code-diff` block for one beat only; end on version number + repo URL. No narration, kinetic captions instead. - + *Rendered from the prompt above, unedited.* @@ -47,8 +53,12 @@ What you can already steer from the prompt, before you've learned any technique. > /pr-to-video Make a ~40-second 1920x1080 changelog video from [PR URL]. Changelog angle: open with the release line, then one beat per notable change — a short label and a one-line "what it does" each. Show at most two `code-diff` hunks across the whole video. End on version + repo URL. Calm male TTS narration, no captions. - - + + *Rendered from this prompt with [PR URL] = heygen-com/hyperframes#2092, unedited.* A changelog trades depth for breadth — many small changes, each a beat, rather than one change explored deeply. Keep code beats sparse so the pace stays fast. A PR doesn't carry its shipping version — the agent finds it from the release tag or the package manifest on main. diff --git a/docs/prompting/code-blocks.mdx b/docs/prompting/code-blocks.mdx index 740f3d3880..3672740911 100644 --- a/docs/prompting/code-blocks.mdx +++ b/docs/prompting/code-blocks.mdx @@ -3,6 +3,8 @@ title: Code animations description: "Prompt code walkthroughs — typing, diffing, highlighting, scrolling — and pick a terminal or editor theme by name." --- +import { DocsVideo } from "/snippets/docs-video.jsx"; + Your PR video from Level 1 named `code-diff` for a single beat and moved on. This chapter is the rest of that catalog: typing, diffing, highlighting, scrolling, and picking a terminal or editor theme by name — for the moments a walkthrough needs to slow down and let the code itself carry the scene. Code is the one subject where the framework does the hard part for you. The [Code Animations](/catalog/blocks/code-typing) blocks handle syntax highlighting, caret tracking, diff coloring, and camera moves deterministically — you describe the *walkthrough*, name the block, and paste your snippet. This page is the vocabulary for doing that well; for turning a real pull request into a code-change video, see [Code and PRs](/prompting/code-and-prs). @@ -44,7 +46,11 @@ The first four are the workhorses of a code *walkthrough* — they keep the code > ``` > Use the `code-typing` registry block. No narration, no image or media files. - + *Rendered from the prompt above, unedited.* @@ -65,13 +71,21 @@ For "here's what changed," hand `code-diff` the before and after and let it colo > added: `const res = await fetch(url, { signal })` > Use the `code-diff` registry block. No audio. - + *Rendered from the prompt above, unedited.* > /motion-graphics 5-second 1920x1080 video. Show a 12-line config file; a highlight band sweeps to line 7 (`timeout: 30_000`) while the surrounding lines dim. Hold with line 7 lit and the cursor blinking. Use the `code-highlight` registry block. No audio. - + *Rendered from the prompt above, unedited — the agent authors plausible surrounding config lines; paste all 12 if the exact file matters.* @@ -85,7 +99,11 @@ For "here's what changed," hand `code-diff` the before and after and let it colo > /motion-graphics 6-second 1920x1080 video. Scroll a ~60-line source file so line 44 (`return dedupeFrames(frames)`) arrives at center and gets spotlighted; ease the scroll and let it settle without snapping. Use the `code-scroll` registry block. No audio. - + *Rendered from the prompt above, unedited.* **Ask the scroll to ease and settle, not snap.** A linear scroll that stops dead reads mechanical. @@ -120,7 +138,11 @@ The [Code Snippets](/catalog/blocks/code-snippet-monokai) blocks are pre-styled > /motion-graphics 5-second 1920x1080 video. A macOS Terminal window in the Ocean profile types `npx skills add heygen-com/hyperframes` character by character, then holds on the typed, unexecuted command with the cursor blinking — no output, no second prompt. Use the `code-snippet-apple-terminal-ocean` registry block. No narration. - + *Rendered from the prompt above, unedited.* @@ -151,7 +173,11 @@ This is the clause in the [full capstone prompt](/prompting/capstone#the-full-pr > **Type (0–7s).** Black-on-charcoal close-up: a cursor types real HyperFrames markup character by character — `
` and a `gsap.timeline({ paused: true })` line. As the typed line completes, the text's baseline extends and becomes **the wire** — the underline literally grows into the timeline and the camera begins its dolly along it. The typed div folds into a compact clip chip (persistent element 3) that drops onto the wire. Kinetic display type states "WRITE HTML." as the travel begins. - + *That clause, rendered — the region cut from the finished film.* *Next: [Data and maps](/prompting/data-and-maps) — the same named-block, quoted-copy pattern, for charts, stats, and maps instead of code.* diff --git a/docs/prompting/color-grading.mdx b/docs/prompting/color-grading.mdx index 9a9c03cb2b..06c8c8d24f 100644 --- a/docs/prompting/color-grading.mdx +++ b/docs/prompting/color-grading.mdx @@ -3,6 +3,8 @@ title: Color grading and film effects description: "Grade media with a fixed-order pipeline — tonal work, hue keys, print and analogue treatments — and know why the source matters more than the payload." --- +import { DocsVideo } from "/snippets/docs-video.jsx"; + Every chapter so far has built the image. This one changes what the image appears to have been *recorded on*. A grade is not decoration applied at the end; it is a claim about the medium — that this came off tape, or a press, or a tube, or a camera with a particular stock in it. Viewers read that claim instantly and they read it whether or not you meant it. Grading attaches to a single `` or `