Loading...
Community presentation
You are laying out a fixed hackathon submission deck, not writing one. The attached source file is the only source of text. Use it exactly. RULES 1. Make exactly 16 slides, one …
Create your own version
Use this visual direction as inspiration for a new Presenton deck.
Use this designCreator prompt
You are laying out a fixed hackathon submission deck, not writing one. The attached source file is the only source of text. Use it exactly. RULES 1. Make exactly 16 slides, one per "Slide number" section, in the same order, with the same titles. 2. Do not add, remove, reword, summarise or "improve" any sentence. Keep every number. 3. Keep every bracketed label exactly: [SOURCED], [PROPOSAL], [PLANNED], [TARGET], [MEASURED], and every citation tag such as [C1], [R5], [V3], [M1]. 4. Do not add statistics, examples, quotes, agenda, thank-you or title-extra slides, speaker notes, stock photos, AI-generated images, or icons that imply facts. 5. Keep tables as tables and cards as separate boxes. Body text at least 14 pt except tables (12 pt). If text does not fit, reduce font size or spacing, never the text. 6. Slide 11 is a diagram: keep its title and legend text and leave a large empty area for an image I will insert. 7. Palette: navy 0E1B3D, teal 0FA3A3, gold C9962B, light grey background. One consistent layout system. Footer: the labels line and slide number. 8. When finished, list every slide where any wording changed, with before and after.
Presentation overview
This community presentation was shared by jay vankar as a complete 16-slide example. You are laying out a fixed hackathon submission deck, not writing one. The attached source file is the only source of text. Use it exactly. RULES 1. Make exactly 16 slides, one … The preview lets you review the full sequence in order, rather than judging the design from a single cover image.
Use it as a reference for planning your own deck: notice how the amount of information changes from slide to slide, where visual emphasis appears, and how repeated design choices help the presentation feel connected. Community examples are inspiration, not locked templates, so you can keep the ideas that fit your audience and replace anything that does not.
Learn from the example
Look at the job each slide performs. Identify where the deck introduces its subject, develops the main points, adds evidence or examples, and moves toward a conclusion.
Notice which element attracts attention first and how headings, supporting text, images, and data are separated. Strong hierarchy makes the intended reading order obvious.
Compare spacing, typography, color, and repeated components across the slides. Consistent rules help varied content feel like one presentation instead of unrelated screens.
Make it your own
Begin with your audience and the decision, lesson, or action the presentation should support. Replace the topic, examples, evidence, and visuals with material you can verify, then edit every slide for one clear takeaway. You can borrow the visual direction without copying the creator's wording or message. Presenton will use this community deck as a design reference while you develop content for your own purpose.
