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.
8 recipes
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.