Pages that scroll like a film
Describe a landing page, a launch, a brand page or a product page and Build designs it the way a studio would: as something a visitor moves through, not a document they read. Scroll is the timeline. A camera move plays under the wheel, a section holds while its argument advances line by line, a range pans sideways, a headline assembles, the ground changes colour as you travel, and the pointer moves things that are not scrolling. Every section behaves differently from the one before, so the page keeps earning the next scroll.
You do not have to ask for any of this by name. It is how Build approaches a page with ambition.
What you get
- One moment people remember. Before any section exists, the page is planned as a feeling curve: what the visitor should feel act by act, and the one peak that gets the best imagery, the quiet before it, and the most room. The ending resolves instead of fading into a footer.
- A page with its own structure. Eight page grammars (a filmic one-shot, a chaptered editorial, a live product surface, a continuous world, a typographic poster, a gallery, a split stage, a rhythmic cutlist) each rule out what the others require, so two pages never share a skeleton. Each one also carries one bespoke move that exists on that site alone.
- A layered hero. Background, subject, foreground and atmosphere are separate planes that move at different rates, with the product anchored where it stands. Imagery is photographic unless your brand is drawn, and it is generated in Corte with your real product or photos as the reference, so the same object appears in every shot.
- Real text, real speed. Headlines and copy are selectable, translatable markup, never baked into an image. Clips are encoded to respond to the hand, with separate phone versions, and the page still tells its whole story for visitors who prefer reduced motion.
- Verified by scrolling it. Build walks the page at dozens of scroll positions on desktop and phone, checks that nothing goes dead, that every line stays readable over the brightest frame beneath it, and that keyboard focus never lands on something invisible, then reviews the result against the brief before reporting back.
How to brief it
A sentence is enough to start. Build will ask the few things only you can answer: what the visitor should believe by the end and what they should do, the journey in your own words, how it should feel stage by stage and the one moment they should remember, and whether you want one continuous world or distinct scenes. Share what you already have: product shots, footage, a brand kit, a Figma. Real assets anchor the page and cut the media cost.
If you would rather not be asked, say so ("use your judgment") and Build writes the brief itself and tells you what it decided.
Before anything renders, Build states the media estimate in credits and waits for a go. A budget you name is a cap it will not cross without asking.
Through the API
From your own agent or the MCP server, list_skills names the procedure
(scroll-craft) and get_skill returns the questions a brief should answer up
front, so a well-written first message with create_build_app can start the
build without an interview.