Author and present slide entrances plus the rest of each slide’s motion, and export visible finished slides instead of hidden entrance frames.
Where: Designer node → Deck kind → slide rail, motion controls, Present, or export menu.
Key ideas
- A slide has a whole time range: A slide’s entrance is not its entire build. Motion after the entrance belongs to that slide until the next slide starts. Presentation plays that build and stops on the last frame that still belongs to the current slide.
- Cue, arrival, and complete frame: The cue is where an entrance begins and may be invisible. The arrived frame shows the entrance completed; the complete frame also includes later beats. Thumbnails, posters, and static slide exports use the finished slide rather than photographing an opacity-zero cue.
- Presentation adds navigation: For a deck, the ordinary Share link publishes the compiled document without the presentation pager and can show only a still first slide. Presentation is the navigable deck with one slide per stop. Use that link when someone must read through the slides.
- Browser PDF export follows the page lifecycle: On desktop, Designer uses its native PDF path. In a browser, fixed-stage artwork such as decks is captured to preserve its exact composition; flowing/reflowing pages use a print document so text remains selectable. Browser print opens the native print dialog: finishing or cancelling returns control to Designer, but the dialog closing cannot prove that a PDF was saved.
- Deck slide roots are isolated from the stage: Slide isolation belongs on authored slide-root boxes, not on the shared stage container. If a successful write leaves the stage incorrectly marked while it contains multiple marked direct-child slides, the editor removes only the mistaken stage marker and preserves each slide identity. It does not guess when slide boxes and motion stops do not match.
Steps
- Create or open a Designer in Deck mode and inspect the actual slides. Selecting a kind alone does not convert arbitrary content into a valid deck.
- Author slide content and motion, including the entrance and any later build beats. Keep speaker notes separate from motion descriptions.
- Present and advance through the deck. Watch the arriving slide and its complete build, then confirm it stops before the next slide begins.
- Use Presentation in the publish/share menu for a navigable deck. Inspect the resulting presentation instead of assuming the ordinary Share action adds navigation.
- For static delivery, export PDF or PPTX where offered and inspect every captured slide, including slides with entrance fades and later build reveals.
- In a browser PDF export, wait for the native print dialog, then finish or cancel it to return to Designer. Verify the resulting file yourself; a closed dialog is not confirmation of a saved PDF.
- Return to the editor and verify the document remains on a readable frame after preview, export, or a tool-driven edit.
Artifact-aware delivery
- PDF is available for non-empty Designer content, not only Document kind.
- PPTX requires a real Deck slide structure; a renamed page is not sufficient.
- Static deck captures use finished-slide timing so delayed elements are included.
- For a fixed-stage deck in a browser, PDF normally prioritizes visual fidelity; flowing page print preserves selectable text. If exact raster capture fails, the deck has a vector-print fallback and some effects may differ.
- Browser print waits for image/font readiness before opening the native dialog. That protects capture completeness but does not mean the user saved the file.
- Video delivery and a motion presentation depend on actual motion content; inspect the export actions derived from the artifact.
Slide isolation repair
The post-write repair only removes an erroneous data-dsn-slide marker from the shared .dsn-stage when multiple direct-child slide roots are already explicitly marked. Child slide identities are retained. The editor then binds unbound direct-child slides only when their count matches the current motion stops. A mismatch is left unresolved for review rather than guessed; visibility-based hiding preserves measurement and layout.
MCP access
Use open_designer, read the returned native declarations, invoke_designer_tool with read_document first, and use the exact available motion/deck tools. The host AI drives the same editor operations without starting a second Flowmo agent. close_designer flushes changes. Designer is not the embedded f0 document iframe.
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.
Troubleshooting
A shared deck has no next-slide control.
Use the Presentation publish action, not the plain document Share link.
Only the entrance plays.
Review the slide’s later beats and presentation playback. The current build plays through the complete slide range; re-open an older saved artifact in the updated editor and inspect it before exporting.
Related guides
- Share, present, export, and reuse Designer artifacts
- Designer AI, motion, interaction, drawing, and media tools
- 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