Step 10 · Presentation flow and export
With content, visuals, assets, charts, 3D details, and local fixes in place, add the last layer: transitions and interaction across the whole deck.
This is not step 8. Step 8 added an effect to a slide. This makes the deck feel continuous when it's presented from the first slide to the last.
Why it comes last
Add it early and every later content or layout edit breaks the timing.
Entrance animations are sequenced against the elements on a slide. Add global motion at step 6, insert a chart at step 7, and that slide's rhythm is broken. Do it once at the end and it's right the first time.
The prompt
Add presentation-level motion and interaction across the whole deck.
The goal is a deck that feels smooth presented end to end.
Add:
1. Slide-to-slide transitions.
2. Section-level transition moments where the topic changes.
3. Entrance animation for key titles, cards, charts, and images.
4. Restrained emphasis on the single most important line per slide.
5. Hover or click interaction only where it makes sense.
6. Light interactive detail on charts, cards, or visual modules where
appropriate.
Constraints:
1. Don't animate everything.
2. Don't make it flashy or distracting.
3. All text stays readable and stable.
4. Chart labels and data stay visible.
5. Interactions stay simple enough to drive live.
6. The animation rhythm is consistent across the whole deck.
7. Optimise performance so presentation mode never lags.
Then summarise:
1. The transition style used across the deck.
2. Which slides got custom interaction.
3. Which slides got special entrance or emphasis animation.
4. Which slides should have their motion reduced or checked by hand.Four kinds of motion, four boundaries
| Type | Good use | Avoid |
|---|---|---|
| Slide transition | Signalling movement from one idea to the next | A different transition on every slide |
| Section transition | Marking a real shift in the story | Making small topic changes feel momentous |
| Entrance animation | Revealing hierarchy in titles, cards, charts | Animating every paragraph and bullet |
| Hover / click | Letting the speaker reveal optional detail | Hiding essential information behind an interaction |
That last "avoid" is the dangerous one. Essential data behind a hover disappears when you export to PDF, and it strands you live if the pointer misbehaves.
The rule: interactions carry optional information only. Essential information is visible by default.
"Consistent rhythm across the whole deck"
Constraint 6 deserves its own note. Consistency matters more here than the effects themselves.
If slide 3's cards fade in sequentially, slide 8's cards shouldn't spring up from below. An audience learns your rhythm without noticing; change it and they have to re-learn, which takes their attention off what you're saying.
Export
This workflow may have used real assets, generated images, charts, 3D, and motion, so the export choice matters.
| Format | Best for | Trade-off |
|---|---|---|
| Present in OpenDesign | Keeps motion, HTML layout, charts, and interaction | You present from that environment |
| PDF / images | A stable visual version to share | Motion and interaction are gone |
| PPTX | Compatibility with traditional tools | Complex HTML visuals don't convert perfectly |
| HTML | Web sharing and archiving | External assets and generated effects need checking |
Recommended: if the deck uses charts, 3D, and motion, present directly from OpenDesign, and export a PDF as a backup in case the room doesn't cooperate.
About PPTX
OpenDesign's export runs through pptx-generator and produces a genuinely editable .pptx — native shapes and text, audited for HTML-to-PPTX fidelity, not one flat image per slide. That's the difference from most HTML-to-PPT converters, which flatten the page.
But editable is not identical. Complex HTML visuals, Three.js scenes, and JS-dependent interaction all degrade in the conversion. Set expectations accordingly: text, shapes, charts, and basic layout survive; the spectacular parts don't.
If you know the deliverable has to be a .pptx, there's an easier route: skip Three.js at step 8 and keep step 10 to basic transitions. Less to lose in translation.
The final check
- [ ] A full run-through on the real machine and projector, first slide to last
- [ ] The screen-share case tested separately (video encoding destroys fine motion)
- [ ] A PDF backup exported and checked for missing slides
- [ ] No essential information hidden behind an interaction
- [ ] No dropped frames on battery
- [ ] A way to jump slides quickly, for when someone interrupts
That's the workflow
What separates a deck that's been through these ten steps from one produced by "generate me a presentation" isn't mainly the model. It's that at every step you made a specific judgement: does this style support my argument, does this slide want a chart, does this motion earn its place.
To turn the workflow into a repeatable skill, see Go deeper / Skills. Every prompt is collected in Reference / Prompt library.