Presentations
Open a .pptx file to edit slides, objects, and speaker notes without leaving the project that contains the supporting research and data.
Navigate and organize the deck#
Use the thumbnail rail to select, add, duplicate, delete, reorder, and move through slides. The canvas shows the active slide at presentation proportions.
Keep slide order intentional. A useful review pass checks whether the title and section sequence still tells the story when the viewer only reads the thumbnails.
Edit slide content#
The presentation editor supports common slide work including:
- Text and shape objects
- Tables and images
- Position, size, alignment, and distribution
- Object layers and ordering
- Fill, line, background, and text formatting
- Image crop and placement
- Speaker notes
- Object inspection and deck audits
Review at both normal zoom and fit-to-slide. Small type, excess text, poor contrast, and off-canvas objects are easier to miss when the whole application is scaled down.
Use the agent for a targeted revision#
Ask for an audit before a broad rewrite:
Audit this deck for text overflow, objects outside the slide, inconsistent title placement, low-contrast text, and slides with more than one main idea. Report issues by slide number and do not edit yet.
Then constrain the revision:
Revise slides 3–5 for an executive audience. Keep every approved number and the current slide size. Use the existing visual system, limit each slide to one conclusion, and leave slides 1–2 and 6–8 unchanged.
For a new deck, name the source and output:
Create exports/customer-research-readout.pptx from @research-summary.docx and @themes.xlsx. Build six slides for product leadership, include source notes, and keep both source files unchanged.
Review a generated or edited deck#
Inspect every affected slide, not only the agent response. Check:
- Title and body text fit
- Image crop and aspect ratio
- Object alignment, distribution, and layers
- Table width and cell readability
- Chart labels, legends, and source values
- Speaker notes and hidden context
- Consistent margins and slide backgrounds
Presentation edits can touch several objects in one operation. If the result is partly wrong, discard the review session and request a smaller slide range.
Save and shared state#
Save with Cmd/Ctrl + S. For a shared presentation, confirm the cloud save or sync state before closing the deck or switching projects. A local file save and a synchronized shared copy are related but distinct states.
Version history supports saved PPTX states. Use it when you need to compare or restore an earlier deck; agent action history is a separate record of agent operations.
Export and handoff#
Nebula Writer saves PPTX files but does not currently provide native PPTX-to-PDF export. For a stable handoff:
- Save and reopen the deck in Nebula Writer.
- Run the deck audit and inspect every slide.
- Open the PPTX in PowerPoint or another compatible presentation app.
- Verify fonts, media, animations, transitions, notes, and object positions.
- Export the delivery PDF there if required.
Use Workflow gallery for a presentation-to-decision-brief example.