Generate a full page¶

Starts from a blueprint rather than a blank prompt, because a page is a sequence with structure, not one big paragraph of instructions — see AI → Blueprints for what a blueprint actually is.

Templates step: blueprint cards — Campaign Landing Page, Program Landing Page, About Us (selected), Contact / Visit Page — with a Choose a direction list of Story-driven (recommended), Institutional, and Bold landing — **1. Templates.** Pick one of the shipped blueprints (or switch to **Describe** and write the page freely). The recommended direction is picked for you — choose another under the template, or change it later from Review.

Review your selections: rows for Template, Direction, Sections, Content sources, and Images, each with an edit pencil; Build settings with Auto build and Guided cards; Advanced expanded with an Anything to emphasize? field; a Build page button — **2. Review your selections.** Every choice on one screen. **Auto** builds everything in the background; **Guided** stops after each section for your approval. **Advanced** holds an optional emphasis note.

Page plan: a draggable list — 1 Hero, 2 Mission, 3 People (with an Events listing-source dropdown and a Band / List toggle), 4 Values, 5 Call to action — each marked Ready — **2a. Sections.** The section order the blueprint produces — reorder, drop sections, or override how a data-driven section (like "People") resolves.

Content sources: a Search pages by title field and a This page (current content) chip marked Current — **2b. Content sources.** Optionally ground the build in real pages — the AI reuses their actual words and images instead of inventing them.

A full-page build always adds to whatever page you had open — there is no separate "create a new page" step. If that page already has at least one section, clicking Build page stops first with "This page already has content," naming the page and asking you to confirm before it adds more; a blank page skips straight past this. Clicking Build page may then also ask you to confirm anything that looks data-driven, before it starts building:

Confirm data sections: a People card saying This section looks like it comes from a view. Should it be a data listing? with No and Yes buttons — A quick sanity check for any section that looks like it should pull from a View, before the build spends a call on it.

Guided checkpoint: Building your page with a section checklist, the freshly landed Hero on the canvas, and a Ready for review card with regenerate, Modify, Approve, and Skip controls — **Guided** mode: each section lands on the canvas, then waits for **Approve**, **Modify** (with a note), regenerate, or **Skip**.

Your page is ready: Hero, Mission, People, Values, and Call to action each marked Inserted, an Undo entire build link, and a Done button — **4. Done.** Every section's status, plus a single **Undo entire build** that restores the pre-build page exactly.

Auto skips the per-section checkpoints and runs straight through the same sequence — useful once you trust the plan from Review and just want the page built.