What does the person have? A live website, a brand kit or guide, only a code repo, or
only footage? That decides the route. Every route ends in the same file,
refs/brand.md, that the concept, visual treatment, titles and cards are built from.
Read the brand's copy and imagery as well as its visual assets: what character does
it express, who does it address, and what should this video's viewer feel? The brand's words and numbers (its
headline, value props, proof) are a separate step: guide-pull-product-highlights.
Routes
| Route | Pick it when | Cost and time | What you get | Load |
|---|---|---|---|---|
| A. Read the live site | The brand has a website (a product page, a project homepage, a community page) | Free, a few minutes in the browser | The fonts as the site loads them, every colour with a count, the buttons with their exact words, every image the site uses, the logo at its largest | references/computed-styles.md, references/collect-images.md |
| B. The brand kit, or the brand questions | The person has a kit (a PDF guide, a Canva brand kit, a Figma file), or knows their brand but has no file | Free | The intended palette and fonts, the logo files, do and don't rules | The questions below; workflow-sales-video-from-canva-deck for a Canva kit |
| C. The repo's own colours or social card | A code project with no site | Free | A palette from the repo's language colours, logo or social card; a mono plus a sans | |
| D. A starter look from the footage | Nothing above exists | Free | Two colours pulled from the set or wardrobe and one heavy display font, proposed, never assumed | guide-add-titles-and-motion-graphics |
Route A beats a screenshot: colours read off a screenshot drift with compression and anti-aliasing, and fonts can't be read off pixels at all. Routes combine: a site plus the person's answers on what the site doesn't show (the active-word colour, mascot rules).
Process
- Capture. Read the available brief, copy and imagery for the brand's audience,
personality and tone before recommending a treatment. Route A: open the site in your browser and run the snippet in
references/computed-styles.md, then collect and download every image withreferences/collect-images.mdintorefs/site/, sheet them (python-contact-sheet,images) and look at every one. Take one screenshot of the hero for reference. Route B: copy the kit's files intorefs/brand/, or ask the brand questions below. - Write
refs/brand.md:- Creative direction: intended audience and the video's purpose from the brief; personality, tone and imagery established by the source, with examples; the impression the video should leave; treatments to favour or avoid and why.
- Label each creative observation source-backed, person-specified or proposed. A bright palette alone does not establish a playful personality; where the source is silent, propose a direction rather than invent brand rules.
- Heading and body font families, weights, case and letter-spacing, and where each loads from (a Google Fonts URL in the page head is common), or the font files.
- Text, background and accent colours as hex, and which one marks the active word in captions.
- The CTA button: shape, fill, border, and its exact words.
- The logo file you chose and its pixel size (The logo, below).
- The site's one signature element (a terminal window, a code card, a chip style, glass pills), which the cards and the end card can echo.
- Mascots or characters, with their rules; the person's do and don't rules, as hard constraints.
- The route you took, and anything you had to substitute.
- With route A, a table of the captured images (
refs/site/images.md) with a proposed use for each.
- Review in the workflow's concept or look gate. Show how the proposed direction uses the brand: a style frame for generated imagery, or a title/card in the live compositor look. Reuse that review rather than add a separate brand-card approval. Resolve any interpretation that would change the route before producing its assets.
The brand questions (route B)
Ask these in one message when there's no kit file, and again for whatever a site doesn't show:
- Creative direction: who this video is for, what they should understand or feel, and any tone or imagery the brand wants to keep or avoid. Use answers already in the brief; ask only what materially changes the recommendation.
- Fonts: files (OTF, TTF, WOFF2) or Google Fonts names for headline, caption and accent type.
- Colours: hex values for primary, accent, shadow or ink, and background, and which one is the active-word colour.
- Logo and wordmark: SVG, or PNG with transparency.
- Characters or mascots: artwork for each pose they want, and any rules for how a character may and may not appear.
- Style references: past videos, a design-system doc, or examples they like and dislike (boxes or none, outlines or flat fills, shadows, tone).
- Words and claims: product names exactly as written, and any numbers that may
appear (only real ones;
guide-pull-product-highlightschecks them).
The logo
- Note its pixel size before planning a full-screen end card. A 444 px site PNG
looked poor on a 1080 end card. Look for a bigger copy: an inline SVG in the header
(the collector saves it), the
og:image(often the logo on a card, 1200 px wide), the apple-touch icon set (180–192 px, the cleanest small mark), the footer, a press or media kit page. - Ask the person for a vector (SVG, PDF, EPS) when nothing on the site is big enough. As a last resort, trace the largest copy to a vector and check every letter against the original before using it.
- Never let an image model redraw a logo: it changes the letterforms. Put the real
file on as an image layer, or
data:URI; an image path inside a text layer renders blank. - The product's own screens often use a different font from the marketing site:
judge the app font from the screenshots (
hn4a-compositor-rebuild-product-screen).
Real people on the site
A founder in a video or a team photo can become the presenter or a reference. Embedded
videos often won't play off-site, and demo pages sit behind lead forms: never submit
one. A video's thumbnail image is often enough; ask before downloading a video. A real
person in the piece follows guide-depict-real-people-and-places, and a spec with a real
employee in it stays private to the client.
Choosing
- Recommend treatments from the brief and the brand. A handmade look might suit a warm, tactile promise; precise diagrams might suit a technical explanation. Those are proposals to show, not conclusions from a colour or product category alone.
- The accent colour is often rare in the count. The top of the colour count is text and background; the accent sits on links, plus signs and one button. Pick the colour the site uses for emphasis, not the most frequent one. Colours sampled from a logo's gradient make good accent text.
- A licensed font can't be embedded (an Adobe Fonts kit, a foundry licence). Use the
closest Google Font, preferably one the site already loads, and say so in
refs/brand.md. - Every text layer names its font family: the compositor aborts on a fallback
(
hn4a-compositor). - The CTA is the site's own. Recreate its button (same shape, colours and words) for the end card rather than inventing a new one.
- No site and no kit for a code project (route C): say which colours you used and why, before building.
Avoid
- Eyeballing colours from a screenshot when the site is live.
- Collecting images without scrolling first: lazy images have no source until they come into view (on a test page, 8 of 10 images without the scroll, 10 with it).
- Putting the brand's logo on a piece that isn't theirs, such as a news short about them. Use their logo only on work made for or with the brand.
- Logos of partner products beyond what the brand itself shows (its integrations list, its own launch video).
Related
guide-pull-product-highlights: the brand's words, numbers and value props.guide-add-titles-and-motion-graphics: what to build with the brand once it's captured.hn4a-compositor: loading the fonts and the spec.workflow-sales-video-from-canva-deck: a Canva brand kit as the source.


