A page recipe is a reusable idea for how a site communicates value. Use one to shape the story, then let your Design Kit control how the result looks and feels.
32 recipes
Is the visitor ready to perform a task right now? The page's first job is an input, a search, a prompt or a sample — explanation comes after the visitor has already started.
Ask visitors what they want to accomplish before explaining the product. Their answer makes a broad platform personally relevant.
Communication idea
Ask visitors what they want to accomplish before explaining the product. Their answer gives them a personal frame for understanding everything that follows.
Put the visitor's query fields above every explanation, then let results, filters and adjacent reassurance do the persuading.
Open with the parameters of the transaction itself, quote price or availability immediately, then offer the account and the wider catalogue.
Let the visitor complete a small, safe version of the core action inside the page, then explain the full product behind it.
Name the one gesture the product is organized around, show it working in the first screen, then unfold the catalogue of actions it reaches.
Give the visitor a finished starting point, show the result it produces, then show exactly what changes when they make it theirs.
Give a runnable start at no cost, show the exact output to expect, then hand off to docs and to a scaling conversation.
Is the product itself the proof? The interface, the artifact or the transformation is the argument. The page's job is to stage it honestly and annotate it.
Lead with finished work, let the visitor browse it by style or job, and reveal the tool only once the output has done the arguing.
Put the real workspace at the centre of the page, annotate the one interaction that matters, then map the workflow around it.
Pick the one interface state that answers the main objection, show it at full fidelity, then explain why it holds at scale.
Walk the trigger, the middle steps, the handoff and the result in the order a real user meets them.
Show the starting artifact, the changed artifact and the single action that did the work.
Establish the human process first, place the agent at one named step, and keep the approval and the audit trail visible.
Show create, revise, integrate and publish as one continuous loop that ends in something live.
Start from an artifact the visitor already recognizes, show the product creating or organizing it, then hand over a template.
Is the blocker risk, scale, cost or governance? Capability is not in doubt; consequence is. These sequences put the counterweight next to the promise instead of three scrolls later.
Make a concrete promise, follow it with dated, unit-labelled scale facts, then tie each fact to the surface that produces it.
Lead with the speed or capability, put the controls that bound it immediately after, then hand over the implementation detail.
State the job, show product evidence, add one quantified customer result, then offer the step that matches the visitor's stage.
Use recognizable customers to establish relevance, then immediately show a product or outcome detail so the logos are never the whole argument.
Name one outcome, then split the page into two honestly different paths: start it yourself, or bring in a team.
Put the value and the terms in the same view: what it costs, what is included, and what the visitor is committing to.
Move the reassurance out of the trust page and put it next to the search box, the listing and the buy button.
Discovery, identity, reassurance and transaction in one loop, closed by a reason to come back.
Is there more here than one page can linearly explain? Catalogues, suites, ecosystems and lifecycles. The risk is not disbelief, it is disorientation — so navigation is the design problem.
Prove the product by the systems it already reaches: name the job, show the connections, then walk one path end to end.
Lead with one umbrella job, arrange the capabilities around it, and give every visitor a route in plus a shared layer to return to.
Present one simple primary job, keep secondary complexity behind tabs, and let depth appear only when it is asked for.
Open with a desired outcome or offer, expose the catalogue as a navigable structure, then make comparison and bundling easy.
Show the core object first, map what extends it, then explain how each addition makes the core more valuable.
Present the suite as one outcome, let the visitor pick by role, industry or module, then return them to the shared platform value.
Put the roles near the top, give each one a tailored scenario, and keep a single shared explanation underneath.
Order the page by stages, from first input to durable outcome, and show the product doing its part at every rung.
Establish the coverage of the whole network, then immediately let the visitor act in one local, personal or code-level place.