Pages & structure
The page editor in Crux — description, page structure, menu structures, evidence links, and viewing an entity on the live site.
Open any Page entity and you get a full editor for what the page is, why it exists, and how it's built. Everything on it can be written by hand or drafted with Generate.
How page structure is organised
Think in four words:
| Concept | What it means |
|---|---|
| Page | The screen or route you're editing |
| Section | A full-width band in the page stack — the container you layout |
| Cell | A space inside a section. A new section starts as one cell; split into columns or rows and resize as needed |
| Item | What you assign into a cell: a Feature, Content, or Menu |
Editor surfaces
| Surface | What it covers |
|---|---|
| Description | What the page is for and why it exists |
| Page structure | Sections on the page, and the Feature / Content / Menu items assigned into each cell |
| Menu structures | Which navigation structures include this page |
| Discovery taxonomy | The Catalog browse/filter model this page uses, if any |
| Used in | Where this page appears across relations and sub projects |
Below these sit the page's evidence links — the research items that justify its existence — and its code references, showing which files in your codebase implement it and whether they're in sync.
Editing structure
In Page structure, sections stack vertically. Use the insert zones between sections (or Add item in an empty cell) to place a Feature, Content, or Menu, or reuse an existing item. Split a section into columns or rows when you need more than one cell, then assign an item into each.
Drag sections to reorder them, or drag an item from one cell to another. Highlighted drop targets show where something can land.
Generate
Each detail field has a Generate action. Crux drafts content grounded in your research graph and project knowledge — a description that cites actual evidence, a structure informed by the journeys you've mapped. Generated drafts are proposals; edit or regenerate until they're right. Revision history keeps every version.
View on site
If your project has a site URL connected and the live site carries crux-attr short IDs, View on site opens the live page with ?crux=ex-… appended — the browser extension scrolls to the entity, highlights it, and shows its why-story. It's the quickest way to check that what's described in Crux matches what's shipped.
Structure flows both ways
Page structure isn't just documentation. Coding agents connected over MCP read it when you hand them an entity with Build with MCP, and Experience scan can propose structure from a live site.
Next
Related articles
Documents: Pages & structure