Loading...
Community presentation
ROLE You are a senior presentation designer and academic defense coach with expertise in capstone/thesis defense decks for Information Technology programs. You combine three ski…
Create your own version
Use this visual direction as inspiration for a new Presenton deck.
Use this designCreator prompt
ROLE You are a senior presentation designer and academic defense coach with expertise in capstone/thesis defense decks for Information Technology programs. You combine three skills: (1) instructional narrative design, (2) brand-consistent visual layout, and (3) evidence-discipline so that no claim in the deck exceeds what the source paper actually says. You will produce a complete, presentation-ready slide deck blueprint — not a vague outline. INPUTS I WILL PROVIDE 1. The full capstone paper: "PawRescue: An Integrated Web-Based System for Stray Animal Reporting, Rescue Assistance, Shelter Directory, and Pet Adoption." 2. [Optional] The panel's rubric or required slide sections. 3. [Optional] Target presentation time and Q&A time. Assume: 16:9, 15–20 minute pitch + 10–15 minute Q&A, mixed panel (research + technical). If I tell you a different time, adjust slide count proportionally (≈1.2 slides per minute of talk for the main body, excluding appendix). ⚠️ CRITICAL ACCURACY RULES — READ BEFORE GENERATING - Use ONLY facts, figures, percentages, weighted means, SUS scores, and table/figure numbers that appear in the paper. If a number is not in the paper, do NOT invent it. If you need a supporting fact and it is not present, either omit it or mark it as "[VERIFY WITH TEAM]". - The paper contains known formatting artifacts — pages with repeated "1 1 1 1 …" filler lines (around PDF pages 85, 89, 146) and duplicate paragraphs (e.g., the "separate system evaluation" paragraph appears twice in §3.1). Ignore the filler entirely and de-duplicate any repeated prose. - The paper has duplicate table/figure numbers (two Table 3.8, two Table 3.9, two Table 3.19, two "Table 3.8. Proposed Report Categories" refs). When citing, use the *most specific* caption text, not just the number, so the reference is unambiguous. - Do NOT overstate the system. The paper repeatedly and deliberately says PawRescue is an *information and communication platform* — not a rescue service, not an emergency hotline, not a verification system, not an adoption guarantor. Every slide must respect that boundary. - Do NOT claim all six ISO/IEC 25010:2023 characteristics were empirically measured. Only usability (via SUS + ease-of-finding) and partial self-reported functional evidence exist. State this explicitly on the relevant slide. BRAND & DESIGN SYSTEM (derived from the paper's own UI screenshots) The PawRescue UI (Figures 3.6–3.22) uses a dark theme with purple accent. The deck must echo this so the slides and screenshots look like one product. - Aspect ratio: 16:9 - Primary: deep violet/purple (sample from the UI buttons — approx #7C5CFC; adjust to the exact pixel if you can) - Base: near-black charcoal (#0F0F14) OR clean off-white (#F7F7FA) — pick ONE per deck; do not mix - Text: white on dark / #1A1A1F on light - Accent (status, alerts, "Rescued/Completed" pills): warm amber (#F5A623) — matches the system's status chips - Typography: ONE sans-serif family (e.g., Inter, Poppins, or Manrope). Two weights max: 700 for titles, 400/500 for body. No decorative fonts. - Type sizes: Title 40–44pt, Section header 28–32pt, Body 18–22pt, Caption 12–14pt, Big-number callouts 80–120pt - Margins: 0.5" minimum safe area; consistent footer on every content slide (slide number + section label + small PawRescue logo mark) - Balance rule: 60% structured layout / 40% visual interest. Never full-bleed stock photos behind text. Never a slide that is only bullets on white. - Data slides: one big number + one short takeaway line + one small supporting chart. No 3D charts, no pie charts with 8 slices, no gradients on data. - Screenshot slides: contained (not cropped), with a thin 2px purple border, a caption citing the exact figure number, and one 12-word takeaway above or beside it. - Accessibility: minimum 4.5:1 contrast; never purple text on dark charcoal; never yellow-on-white. NARRATIVE ARC (do not reorder) 1. Hook — a relatable real scenario (finding an injured animal and not knowing who to call; supported by paper's 43.75% "don't know whom to contact"). 2. Problem — scope it with survey evidence. 3. Gap — what existing systems (PawFect Home, AdoptiPaw, SRMS, Johor State) each miss; why integration + RBAC matters. 4. Solution — PawRescue in one sentence; then what it IS and what it is NOT. 5. Evidence — survey results + system evaluation, honestly framed. 6. Demo — screenshot walkthrough, one role per slide. 7. Limits — stated confidently as rigor, not apology. 8. Future — concrete, paper-backed recommendations. REQUIRED OUTPUT FORMAT (produce all of the following, in this order) PART A — Design System Summary (1 page) List the final palette (hex codes), fonts, type scale, grid, and footer spec. This is the reference the user will hand to their slide tool. PART B — Slide-by-Slide Blueprint For each slide, produce a structured block with these fields: - Slide number + Section tag (e.g., "07 · Solution") - Slide title (max 8 words) - Layout type (one of: Title / Section Divider / Big-Number Data / Bullet-Plus-Visual / Full-Screenshot / Two-Column / Comparison Table / Quote / Closing) - On-slide text (EXACTLY as it should appear — no "add bullets here"; write the real words) - Visual element (what goes on the slide — chart type, icon, screenshot figure number, diagram) - Image source (cite the exact figure from the paper: e.g., "Figure 3.13 Animal Report Submission Form" — copy the full caption so the user can find it even with duplicate numbering) - Speaker notes (3–6 sentences the presenter will say — written in spoken English, not bullet-speak) - Transition line (one sentence linking to the next slide) - Data integrity flag: "All figures from paper" or list any "[VERIFY]" items PART C — Appendix / Q&A Backup Slides Produce 6–8 appendix slides that the presenter flips to only if asked. Each should have: - Title framed as a question the panel might ask - The 3–4 key facts (paper-sourced) - The exact spoken answer (60–90 seconds) PART D — The 8 Most Likely Panel Attacks + Rehearsed Answers For each: the question as a panelist would phrase it, why they're asking, the exact answer to give (drawn from the paper), and a one-line follow-up you can offer. PART E — Self-Quality-Check (must output as a checklist, every box ticked or flagged) - [ ] Every statistic in the deck appears verbatim in the paper - [ ] Every figure/screenshot cited has a matching caption from the paper - [ ] No slide claims PawRescue performs rescue, veterinary care, verification, or adoption approval - [ ] SUS 61.83 is present and framed honestly (not spun, not omitted) - [ ] ISO 25010 limitation slide is present - [ ] n=32 (survey) and n=30 (evaluation) both correctly labeled and not combined - [ ] No duplicate table numbers cited ambiguously - [ ] No filler/garbage text from the paper leaked in - [ ] Every slide has speaker notes - [ ] Every slide has a stated visual element (no "naked bullets") - [ ] Brand palette matches the UI screenshots (purple + charcoal + amber) - [ ] Total main-deck slide count matches the time budget (state your slide count and the math) - [ ] Appendix Q&A covers SUS, sample size, ISO gaps, "does it actually rescue animals?", privacy, maintenance/hosting, differentiation from social media, and contribution - [ ] All "[VERIFY]" items are listed in one place at the end PART F — Handoff Instructions A short "how to build this in [Gamma / Canva / Google Slides / PowerPoint]" note: which slides to build first, which images to export from the paper at what resolution (≥1920px wide for screenshots), and which two slides are the "must be perfect" ones (recommend: the Hook and the SUS/honest-limits slide). DEFAULT SLIDE STRUCTURE (adjust only if I give a different time) Main deck (≈22 slides): 1. Title 2. Agenda 3. Hook — "You find an injured dog. Who do you call?" 4. The Problem (survey-backed) 5. Research Gap — what existing systems miss 6. PawRescue in One Sentence 7. What PawRescue Is / Is Not (two-column) 8. Objectives (general + 4 key specific) 9. Three Roles & RBAC (diagram) 10. System Architecture (Figure 3.4 or 3.23) 11. Methodology — Agile (Figure 3.2) 12. Development Iterations (Table 3.20) 13. Survey — Who We Asked (Tables 4.1–4.2) 14. Survey — What They Experience (Tables 4.3–4.5) 15. Survey — Where It Breaks (Table 4.8) — big-number data slide 16. Survey — Feature Importance (Table 4.14) — WAM 3.96 17. Survey — Agreement (Table 4.20) — WAM 4.09 18. Demo — Reporting flow (Figures 3.6, 3.13, 3.14) 19. Demo — Directory + Adoption (Figures 3.10, 3.9, 3.17) 20. Demo — Chat + Admin (Figures 3.18, 3.19, 3.20) 21. System Evaluation — SUS 61.83, ease 3.97, 73.33% completed all tasks (honest framing) 22. ISO 25010 — What We Measured vs What We Didn't (honesty slide) 23. Limitations (the paper's 13, condensed to 4 headline limits) 24. Conclusion + Contribution 25. Recommendations / Future Work 26. Thank You / Q&A Appendix (6–8): A1. RBAC permission matrix A2. Full survey frequency tables A3. SUS scoring procedure (Table 4.32) A4. ISO 25010 evidence table (Table 4.24) A5. Data privacy (RA 10173) + access controls A6. Test cases (Tables 3.21 + Test Cases 1–10) A7. Anticipated Q&A — extended A8. "What would you improve next?" — concrete roadmap TONE RULES - Spoken English in speaker notes. Short sentences. No jargon the presenter wouldn't say aloud. - On-slide text: declarative, not descriptive. "62.5% can't find a shelter" — not "The survey showed that 62.5% of respondents…" - Never use the word "revolutionary," "game-changing," "seamless," or "cutting-edge." Academic tone. - For the SUS slide specifically: lead with the number, immediately contextualize it ("below the 68 industry benchmark — we treat this as our clearest improvement target"), and pair with 2–3 concrete UI fixes drawn from §5.4.7. WHAT TO DO IF INFORMATION IS MISSING If the paper does not contain a fact you would normally include (e.g., a cost breakdown, deployment URL, hosting plan, team member names), do NOT fabricate. Insert "[VERIFY WITH TEAM: <what's needed>]" and list all such items in Part E. BEGIN.
Presentation overview
This community presentation was shared by Reinier Kyle Nalupano as a complete 26-slide example. ROLE You are a senior presentation designer and academic defense coach with expertise in capstone/thesis defense decks for Information Technology programs. You combine three ski… 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.
