Generating Slide Decks
Slide deck generation creates an image-rich, brand-governed, self-contained HTML deck from project content. Decks are grounded in your sources and can be edited conversationally after generation, then exported to PowerPoint (.pptx) or PDF.
Where Slide Deck Generation Starts
Section titled “Where Slide Deck Generation Starts”You can start from:
- Studio mode selection
- Magic Generate
- Quick actions in the app shell
Core Slide Deck Inputs
Section titled “Core Slide Deck Inputs”Slide deck generation supports:
- Output language selection
- Slide count
- Deck look template (Auto, Editorial, Corporate Clean, Bold Impact, Minimal Mono) or an approved brand template
- Audience/profile fields
- Optional focus topic and steering instructions
Language Selection
Section titled “Language Selection”Before you generate a deck, choose the Output Language field in the slide deck setup screen.
- The selected language controls the generated slide titles, body copy, and supporting labels in the initial deck.
- The selector now exposes the full supported language catalog available in the platform.
- The rest of the deck workflow stays the same after generation: open the artifact, review the deck, then continue into deck editing or export.
Brand Template Support
Section titled “Brand Template Support”If brand deck templates are available, you can select a brand template asset during generation.
After Generation
Section titled “After Generation”Open the artifact detail page to review the deck in the Slide Deck Editor: page through slides, edit title/body/visual layers, revise the deck conversationally with chat, and export to PowerPoint or PDF.
Related Guides
Section titled “Related Guides”Advanced Usage Notes
Section titled “Advanced Usage Notes”Use these patterns to get more predictable results:
- Keep inputs specific and scoped to one intent per generation request.
- Save intermediate outputs often, especially before running major edits or regenerations.
- Use review and assignment workflows early to reduce rework late in the lifecycle.
Troubleshooting
Section titled “Troubleshooting”If results are not what you expected:
- Verify source quality first (missing context, inconsistent structure, or conflicting inputs reduce output quality).
- Re-check selected options and audience/profile settings before re-running.
- If a job fails repeatedly, wait briefly and retry once; then escalate with the artifact or job context.
Frequently Asked Questions
Section titled “Frequently Asked Questions”Why did quality change between runs?
Section titled “Why did quality change between runs?”Different input context, settings, and model/runtime conditions can produce different outputs.
Should I regenerate or manually edit?
Section titled “Should I regenerate or manually edit?”Regenerate when the core structure is wrong; manually edit when only wording, ordering, or style needs adjustment.
What is the best way to reduce iteration cycles?
Section titled “What is the best way to reduce iteration cycles?”Start with clear scope, run smaller batches, and use review checkpoints after each major step.