marketing-vs-product-ui says why marketing tolerates more expression. This node is the build checklist: what a landing page, blog, docs site, or changelog has to do to be fast, readable, and honest. A visitor sees the page once, not a hundred times a day, so the animation budget is larger; it is still small, and restraint is the house style.

Motion

Motion maps to user input. No scroll-triggered fade-ups, no scroll hijacking, no parallax that isn't 1:1 with scroll, no auto-advancing carousels. If the user didn't cause it, cut it.
Intro animations play once per session. Gate hero reveals and logo sequences with sessionStorage so internal navigation skips them but a genuinely new visit sees them. localStorage would kill them forever.
A product demo is a figure, not page motion. One looping or play-once demo may lead a viewport: stopped offscreen, a poster under reduced motion, and a visible pause when it moves for more than 5 s (stageshow-reconciliation, [[MOC-faux-ui]]).
Hover-revealed content still obeys touch-and-focus: gated, and never the only route.
Readable on the first frame. In taste-skill's capture of 99 Awwwards Sites of the Day (October 2026), 60 opened on a loading screen and a third were still unreadable 4.5 s after load. The model panel's design marks were the same whatever the wait; only usability fell. No preloader; the title readable on first paint; any load sequence over by 1.2 s. Scroll hijacking scored 6.01 on usability against 6.50 for pages that scroll. Only 35 of 99 had any prefers-reduced-motion rule, and under it the finished state must show, never a hidden one (prefers-reduced-motion).

Performance

Pre-render everything. Blog, docs, changelog — build-time generation with revalidation, never request-time fetching.
Kill layout shift at the source. Preload fonts (<link rel="preload" as="font" type="font/woff2" crossorigin>) and above-the-fold images; lazy-load the rest. See performance-discipline.

Structure

Content lives in the DOM. Hover-revealed nav submenus are visually hidden, not mounted on hover — crawlers and assistive tech need the real markup.
CTAs know who's looking. Logged-out: "Get started". Logged-in: "Open app". Never "Sign up" to a signed-in user.
First viewport: brand, one headline, one supporting line, one CTA group, one dominant visual. No card soup, stat strips, or floating promo chips — see unslop-pass.
Code-built illustrations get role="img" + aria-label, user-select: none, and pointer-events: none unless interactive.

Docs, blogs, changelogs

Docs are for copying. A copy button on every snippet; every page exportable as markdown (a "Copy as Markdown" button and .md URLs such as /docs/getting-started.md) — people and the models reading your docs both want it; a visual example for every concept.
Blogs and changelogs are feeds. RSS at predictable paths (/blog/rss.xml, /changelog/rss.xml); text-wrap: balance on article headings.

Pre-ship checklist

When to apply

Creating or reviewing any public-facing page, and any time parallax, a carousel, or a scroll animation is tempting.

Gotcha

"Marketing tolerates more motion" is read by agents as "marketing wants more motion". The permitted extra is one first-run hero moment. A page where every section animates in is the AI-default look, not expression. taste-skill's inspector fails a page where fewer than 8 elements move; this graph does not adopt that floor.

Sources

Emil Kowalski's design-engineering practice on marketing pages, distilled by HKTITAN.
Leonxlnx, taste-skill v2.1.1 (MIT, HEAD a9c73c3): skills/taste-skill/references/motion.md §2 and §9 (99 Sites of the Day captured October 2026: preloaders, readable time, reduced-motion rules, hijacking's usability score; scores are model-panel judgements) and scripts/lib/rules.mjs (still-page, not adopted).
Related: marketing-vs-product-ui, performance-discipline, unslop-pass, viewport-custom-design.