Website Video

---
name: website-video
description: Turn a website into an original animated brand film using its real product, facts and identity. Show the website itself only when requested. Load once, before asking, when the user names a site or URL.
---

# Website video

The website is source material, not the video. Ask which visual approach the
user wants: their own images, website photos, illustrations or a mix. Build a
brand film about what it offers in that approach, not a tour of its pages.
Build it as the `motion` skill describes; this page adds what is specific to
sites. Demonstrate the website itself only when the user requests a walkthrough.

## Ask (on the motion skill's single card)

Use the shared visual-approach question from `motion` when unsettled, ahead of
an optional idea pitch. Adapt its choices to this job; keep the card to four
questions total and skip choices the brief or requested reference already settles.

- "What should people do after watching?" Visit, sign up, buy, book. Offer the
  site's own call to action as recommended.
- "Where will people mostly watch this?" (from the `motion` skill).
- "Should it have music?" (from the `motion` skill).
- "Which idea should we go with?" Pitches below, plus "Let GG Motion choose".

Without a URL, end with one plain line asking them to supply the address.

## Gather the site

Work inside the fresh video folder created by the `motion` skill. Capture the
requested page once (`hf capture <url> -o sources/site`) there and read its
headline, sections, colours, fonts and images; they are the brand. An earlier
video about the same URL is not a source or design reference unless the user
explicitly selects it. Look at only the images you will use.

Page screenshots are research, not default scene backgrounds. Follow the chosen
approach: individual source images for photo-led work, original HTML/SVG/CSS illustrations
for illustrated work, or both for a mix. Keep the real logo and brand fonts.
Do not sneak photo-led scenes into a request for illustrations or replace the
user's photos with illustrations.
Preserve real packaging and logos; illustration must not invent product
features, ingredients, outcomes, prices or testimonials. Do not run image
generation unless the user explicitly requests it.

## Ideas from the subject, not the page layout

Pitch actions specific to what the business offers, not ways to reveal a
screenshot. Each idea needs a visual subject doing something beyond a text
entrance; do not add a planning document.

- **The product in action.** A real product cutout meets illustrated elements
  grounded in the source: shapes pour, mix, unfold or assemble around it. One
  object carries the viewer into the next scene.
- **A change you can see.** Illustrate the problem becoming the solution: a
  tangled path straightens, scattered pieces organise, a process completes.
  Metaphors must not imply unsupported results or literal product behaviour.
- **A small world around the brand.** Build a scene from its subject, colours
  and shapes. Objects interact with words and transform into the final product
  and call to action. Do not default to floating decorative blobs.

## If a website walkthrough is requested

Use real UI and reproduce the specific interaction being explained as HTML.
Show a cursor only where it operates something; use close-ups readable at the
output size. Carry a selected component into the next scene rather than
cycling through screenshots. A screenshot is appropriate evidence of the
interface, not a substitute for the action.

## Pitfalls

- Website screenshots with animated text over them: not a brand film.
- Product photos on successive cards with only zooms, fades or text entrances.
- Following the site's section order instead of telling a story about its subject.
- Browser frames, scrolling and cursors when the brief is not a walkthrough.
- Decorative motion unrelated to the product, or invented visual claims.
- Text from the site shown too small to read.