Share, present, export, and reuse Designer artifacts

Publish a compiled multi-page runtime, present decks or motion, export HTML/PDF/PPTX/video where valid, and save a Designer artifact as a reusable f0 inline code element.

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.
Preview and Live are distinct: The sharing lifecycle supports review/staging and live publication, along with unpublish. Use the live target only when the user deliberately asks to make the artifact public.
A link is not access: The share section publishes a public address. Giving a named person access to the project - as a collaborator, with a role - is the app collaborator dialog, reached from the same menu. They are different acts and the menu keeps them apart.
Reusable f0 component: A Designer creation can be saved as an f0 inline code element. Its exposed fields become normal editable controls and its compiled interaction/motion remains attached.

Steps

Review every page, slide, interaction, beat, and exposed field in Preview.
Open Share/Export and choose the target the artifact actually supports.
For a multi-page share, confirm page names and the index page before publishing.
Use Present for a real deck or motion timeline. Use PDF for non-empty content, PPTX for a true deck, or video when motion beats exist.
Copy/share the resulting address or download the exported files. Use Unpublish when the published runtime should stop resolving.
To reuse the artifact in f0, save it as an inline code element and verify its exposed controls in the sidebar/timeline.

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.

What the published runtime includes

Compiled page HTML and CSS.
Motion and interaction runtime.
Every non-empty page.
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.
Saving as an inline code element does not convert arbitrary HTML into native f0 layers.
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.