Choose the right page type, add and target pages without losing your place, work across independent pages or deck slides, and understand fixed versus fluid stage behavior and the pages dataset.
Where: Designer surface -> page tabs (add a page, rename, change its type) or the deck slide rail
Key ideas
- A page type configures the workspace: The type chooses a scaffold, chrome, AI context, stage sizing, and relevant delivery actions. It does not constrain what HTML can contain and does not migrate a document when changed. Type lives on the PAGE, so one project can hold a landing page, a deck and a dashboard at once.
- Pages are independent documents: Each page has its own HTML, undo state, comments, motion, and exposed fields. Nothing is implicitly shared between pages; a connected Design System is applied to all of them.
- Deck slides are pages with stops: Deck uses a thumbnail rail and fixed 1920 x 1080 stage. Named data-dsn-slide stops drive presentation order, motion cue output, PDF/PPTX eligibility, and slide navigation.
- pages_out is structured data: The output is a typed dataset with page names, filenames, and compiled documents. It can feed Items/List workflows without flattening all pages into one HTML string.
Steps
- Choose Page/Website clone for fluid web work, Deck/Video/Image for fixed stages, Prototype for screen flows, Document for reading, or Live artifact/WebGL for runtime-driven output.
- Add and rename pages. Use tabs for normal kinds and the slide rail for Deck.
- Switch pages deliberately: each page retains its own content and comments, while switching clears the undo stack belonging to the page you leave.
- Review every page before sharing or export; publication compiles all pages, not only the active one.
- Connect pages_out to a List/data consumer when downstream processing needs one record per page.
Fixed and time-based stages
- Slides and Reel & video edit: fixed 1920 x 1080.
- Ads: the master size you picked, with its sizes and variations.
- Landing page & web, Documents & research, Wireframes & mockups, HTML email, Live dashboard: fluid.
- Slides, Reel & video edit and Animation & motion expose the primary time-based chrome. Scroll scrub is intentionally unavailable on a fixed time-based stage because its timing is not page scroll.
Page AI tools
- list_pages reads names, ids and types.
- add_page creates a new typed page and makes it active.
- set_page_type retypes the active page.
- read_page inspects another page without changing the visible tab.
- read_slides returns a deck page slide by slide, numbered from 1.
- switch_page moves the person to another page and is a view-moving action, not the way to reach a page for editing.
- Every document and media tool takes an optional page_id, so the AI can read and edit a page you are not looking at - and two conversations can work on two pages at once.
Publishing names and routes
- Every non-empty page is compiled.
- The first non-empty page becomes index.html.
- Other filenames derive from distinct page names/slugs.
- Empty drafts are omitted from exported files.
- A multi-page share keeps routes distinct instead of overwriting one page with another.
Complete slide builds and honest delivery choices
Designer deck playback includes the entrance and all later beats up to the next slide. Posters, thumbnails, PDF, and PPTX captures use completed-slide timing. Plain Share is the compiled document without a pager; use Presentation to deliver a navigable deck.
- PDF is available for non-empty content, not only Document kind.
- PPTX is enabled by actual Deck slides declared in the motion structure.
- Card-driven deck generation creates a deck-shaped artifact rather than an unrelated single page.
- External artifact storage and exported files retain the content needed for restoration.
- MCP open_designer returns current native tool declarations, including the current motion/deck capabilities; invoke those through invoke_designer_tool, then close_designer to save.
Standalone projects, direction, kit, review, and resource workspaces
Designer now operates as a dashboard project as well as a Flowgen node. Every page remains in one shared document with per-page type and undo, collaborators can occupy different pages, and supported editor cards can be promoted to a project and explicitly pulled back. Media, Brain, Design system, art directions, the immersive section kit/library, and rendered page review are first-class workflows rather than implicit prompt conventions.
- Use list_directions/set_direction before building, then check conformance.
- Use list_kit_sections and insert_kit_section to assemble tested structures with slot and pin metadata.
- review_page looks at rendered screenshots, returns ten 1–5 scores and at most six fixes, and normally allows two rounds.
- Sharing, Presentation, PDF/PPTX, image/video output, and Flowgen pull-back are distinct delivery paths.
Tips
- Use short unique page names before sharing.
- For repeated structure, use the Design System and copied components rather than assuming page-level HTML is shared.
- Read another page first when the AI only needs context; switch only when it must edit.
Limitations and important notes
- Page switching does not preserve the undo history of the page being left.
- PPTX export requires a Slides page with real slide markers, not merely several arbitrary pages.
- Scroll-scrub conversion is unavailable on a fixed time-based stage.
- Media and Design system are hosted views; markup written into them is not what renders.
Troubleshooting
Only one page appeared at the root URL
The first non-empty page is index.html. Open the other page slugs or review the multi-file export.
PPTX is unavailable
Use Deck kind and create real slide stops; several ordinary pages do not make a deck.
Related guides
- Designer node: complete reference
- Share, present, export, and reuse Designer artifacts
- Items List: typed records, AI Fill, views, and repetition
- Designer decks: full slide builds, transitions, and finished-slide exports
- Designer projects, pages, promotion, and the Flowgen round trip
- Designer art directions: choose, customize, and verify a visual language
- Designer immersive section kit and the 181-section library
- Designer visual review: measured checks, fix rounds, and the ship threshold
- Designer resource surfaces: Media, Brain context, and Design system