# Website sitemap, wireframes and page content

## What it does

The first stages of a website build. The sitemap agent decides which pages the site should have; the wireframe agent turns the approved pages into section-by-section blueprints; then Nexus sets up one content item per page so each one can be written. Each stage ends with a review and an approval before the next starts.

## Set it up

Both agents need the client's G2M and brand identity on file. The keyword universe is optional: with it, each planned page is checked against search demand; without it, demand shows as unverified.

## Use it

### Sitemap

- **Agent:** Website Sitemap & IA Architect (`web-sitemap`)
- **Model tier:** Sonnet · **cost cap per run:** $4.00
- **Needs:** sitemap, web_crawl

1. **"Build the sitemap for the client."** Nexus asks whether to start from the current site (it crawls it) or from a page list you give it (pasted, or a sheet). It also looks at how competitors structure their sites.
2. The finished run has no link of its own. **"Show me the proposed sitemap."** renders it as a Google Sheet: one row per page, a `keep` column, and a demand verdict for each page.
3. ✋ Edit the sheet: set `keep` to FALSE for pages to drop, fix slugs and page types, add notes for merges.
4. **"Approve the sitemap."** locks the structure. **"What pages are planned for the client?"** reads it back at any time.

### Wireframe

- **Agent:** Website Wireframe & UX Architect (`web-wireframe`)
- **Model tier:** Sonnet · **cost cap per run:** $2.50
- **Needs:** web_crawl

1. **"Build the wireframes for the client."** Each page type gets a blueprint: the order of sections, what each one says, CTAs, where proof goes, FAQ slots and the schema plan. This is structure, not visual design.
2. Big site with many page types? Run it one type at a time ("Build the wireframe for the service pages."); the runs add up into one proposal.
3. **"Show me the wireframe doc."** delivers it as a Google Doc. ✋ Review it, then **"Approve the wireframe."**

### Page content

**"Create the content plan for the new website."** adds one content-calendar item per approved page, seeded from its wireframe. Nothing is written yet: draft each page on its own ("Write the page [title].") so every page is reviewed and approved separately (see content production).

## Troubleshooting

- **The sitemap run finished but there's no link.** Expected: the review sheet comes from "Show me the proposed sitemap."
- **You want structural changes to the sitemap** (merge two pages, turn a page into a homepage section). Edit the rows in the sheet, or ask for a re-run with the changes, then approve.
- **The sitemap agent stopped: no sitemap reachable.** The current site has no readable sitemap. Re-run with a page list.

## Prompts

- "Build the sitemap for the client."
- "Show me the proposed sitemap."
- "Approve the sitemap."
- "What pages are planned for the client?"
- "Build the wireframes for the client."
- "Show me the wireframe doc."
- "Approve the wireframe."
- "Create the content plan for the new website."