Distinguish collaborator access from public links, choose document-aware presentation and downloads, and manage staging links separately from a permanent live website.
Where: Designer surface -> Share / Present / Export; or save/reuse actions
Key ideas
- Delivery follows artifact structure: Share is available for non-empty artifacts. Presentation uses slide stops for decks or the motion timeline for animated work. PDF, PPTX, and video only appear when the artifact has the structure each format needs.
- Published output is compiled: The share pipeline compiles HTML, CSS, MotionSpec, InteractionSpec, fields, and every non-empty page into the runtime. It is not a screenshot of the editor.
- People, links and files are separate: The menu starts with Share with people for collaborator invitations and roles, then separates links and files. Public document/presentation links do not grant project membership.
- Review links and the permanent site are different: Named site/presentation links and the permanent live website each have their own saved address and update/offline lifecycle. Updating one destination does not update another.
- Downloads are snapshots: PDF, PPTX, HTML/ZIP, image and video are exported files. A later document edit does not change a file already downloaded; export again when its source changes.
Steps
- Review the intended page, slide, interaction, beat and exposed fields in Preview, and confirm the save state.
- Open Share & export. Use Share with people for collaborator access; use the links-and-files area for public destinations and downloads.
- Choose the artifact-supported action. A project-level site/link manager can hold separate named site or presentation links and a permanent site; a node-backed view may show its available public/presentation controls.
- For a multi-page website, confirm page names and the index page. For a deck, use Presentation for navigation; use PPTX only when actual slide stops are present.
- Choose PDF for a supported printable document/page, and video only when the document has motion. Inspect the actual downloaded file or open the published URL.
- Before Publish, Update or Take offline, confirm the exact destination and current hosting/domain details. After source edits, update only the intended live destination and test it again.
Capability rules
- Share: any non-empty Designer artifact. Giving a PERSON access is the separate collaborator dialog, not the public link.
- Present: deck slide stops or a motion timeline.
- PNG: any page. It is captured at the width the canvas is showing, and a fixed-stage page (an ad, a slide, a reel frame) exports at its own canvas instead, at 1x or 2x.
- PDF: a deck, ad or logo is one high-DPI raster per slide at the stage size; a flowing page or document is printed as settled vector so the text stays selectable; the desktop app prints its own.
- PPTX: a Slides page with real slide markers. Editable by default - boxes become shapes, headings become text boxes, and only what PowerPoint cannot draw (a gradient, a backdrop blur, a mask) becomes one small picture each - with an exact-picture fallback that cannot be affected by a missing font.
- Video: artifact with motion beats, rendered in the tab with WebCodecs or by the desktop app. Silent by contract on both paths.
- Multi-page files: first non-empty page is index.html; remaining pages receive distinct filenames.
Menu sections and destination lifecycle
- Share with people opens the collaborator/role dialog.
- Links and files contains public document/presentation links and supported downloads.
- The project link manager can add, rename, update and take individual destinations offline.
- The permanent site section owns the canonical live website/domain lifecycle; it is not the same row as a staging/review or presentation link.
- Downloads remain point-in-time files and must be generated again after source changes.
What a published runtime includes
- Compiled page HTML and CSS.
- Motion and interaction runtime.
- Every non-empty page when a multi-page project share is selected.
- Design-system treatment applied to all pages.
- Hosted media URLs and supported runtime dependencies.
- Exposed-field defaults needed by the artifact.
Versions and recovery
- Designer conversation and versions persist.
- Rewind to a previous message restores the corresponding authoring state.
- The editor can detach, move, and resize without changing the stored artifact.
- Unpublish changes delivery state; it does not delete the Flowgen node or authoring history.
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 the poster output for catalog thumbnails and the share runtime for the real interactive result.
- Export a true deck to PPTX only after checking every slide boundary.
- Keep review/staging links separate from live publication in automated flows.
Limitations and important notes
- A static document without motion cannot render a meaningful video.
- Ordinary pages without a Deck slide structure do not qualify for PPTX.
- A published share may still depend on hosted media URLs.
- Source availability does not prove the current account has a configured hosting worker, domain, or live publication.
- Rendered video carries no sound on either the in-tab or the desktop path.
Troubleshooting
Video export is missing
Author at least one valid motion beat and confirm the timeline is part of the document.
An exported page is not index.html
The first non-empty page becomes the index. Reorder pages or remove the leading empty draft.
Related guides
- Graphics node: complete reference
- Designer page types, pages, slides, and responsive stages
- Designer AI, motion, interaction, drawing, and media tools
- HTML Export node: export standalone website pages
- Designer decks: full slide builds, transitions, and finished-slide exports
- Designer mode: the Flowgen canvas, typed documents, and legacy projects
- Designer art directions: choose, customize, and verify a visual language
- Designer immersive section kit and the 181-section library
- Designer visual review: quick checks, full review, and scoped QA
- Designer resource surfaces: Media, Brain context, and Design system