Product introduction: turn scattered material into a visual draft
The hardest part of a presentation often comes before the first slide: you have plenty of material, but need to decide what comes first and which evidence belongs together. Gamma combines writing and layout in one creation process. It makes presentations, documents and other content; this article focuses on making a presentation in Gamma 5, rather than covering every use of the product. Introducing Gamma 5
Here is a teaching scenario: a community bookstore needs to report on a weekend reading group to its partners. It has an event description, registration records and photographs, and wants a four-page presentation. Names and numbers should come from the real material; a generated chart cannot replace the original records. A “card” is the unit that holds a page of content in Gamma.
Core workflow: from a four-page plan to a file you can deliver
-
Describe the audience and task. Paste notes or attach material in the dashboard prompt bar. For this example: “Make a four-page reading-group report for partner bookstores. Cover the goal, actual participation, feedback and next steps. Mark missing data for completion.” Choose Plan, which discusses a plan before generating. Express skips questions and plan review when the direction is already clear. Creation modes
-
Check the story before it is built. Answer questions about the audience and goal, review the plan, then confirm generation. If it spends too much space on the bookstore's history, bring the focus back to this event. Cards appear as generation progresses. When it finishes, review each page, checking numbers and arguments before the appearance. That order is an editorial suggestion, not a substitute for checking the source material.
-
Make each edit request small enough to judge. Use the switch at the editor's top left to enter AI editing mode, then click the target element. Confirm that it appears in the selection in the left chat before entering your request. For example, ask to shorten the second page into three points without also restyling the entire deck. Compare the before and after, then accept or restore all changes from that request. You cannot accept individual changes within it. To keep only part, restore the batch and send smaller requests, or edit manually afterward. AI edits and restoration scope
-
Choose the right layout freedom. A grid adjusts content within its cells, which suits three neatly aligned pieces of feedback. For a photograph and quotation that need exact positioning, switch the relevant block to Freeform. It cannot be converted directly back to a grid; you can use Undo immediately after converting. Do not treat it as a switch you can freely toggle both ways. Grids and freeform editing
-
Review the delivered file too. Open Export from Share, choose PDF or PowerPoint as needed, and set the range to All cards to export all four pages. Exports follow Present mode, and fonts or some visual effects may change. Open the actual file, confirm that all four pages are there, and check line breaks, images and tables. Send PPTX to partners who need to keep editing and PDF to those mainly reading. Check the free plan's export branding before delivery as well. Export guidance
Design lessons: place checks where mistakes are cheaper to fix
Review the story before the visual details. In the reading-group example, the wrong reporting focus affects all four pages, while a photograph's position affects only one area. Plan brings the first decision forward, before the user faces a whole visual draft. It adds a confirmation round; someone with a complete outline can choose Express. The transferable principle is to place checks according to the reach of a mistake, rather than adding a confirmation box to every step.
Make the scope of an edit understandable. A selection identifies the object to change, while accepting or restoring a whole request defines the scope of one decision. If a request changes the title, explanation of numbers and style together, the user may like two changes but have to restore the entire batch. The harder an action is to split, the clearer its goal needs to be before it starts. Clear scope does not make every generated result correct; it helps locate the mistake.
Layout freedom has a specific cost. A grid maintains orderly relationships for the user; freeform layout hands positioning decisions back to them. They solve different problems, so “more freedom” alone is not a useful verdict. Before converting a block, decide whether you need orderly reflow or exact placement. A useful interface should also make the available route back clear.