Loading...
Community presentation
I will provide five individual Capstone II defense presentations. Your task is to create a completely new presentation from scratch. Do NOT modify or merge an existing presentat…
Create your own version
Use this visual direction as inspiration for a new Presenton deck.
Use this designCreator prompt
I will provide five individual Capstone II defense presentations. Your task is to create a completely new presentation from scratch. Do NOT modify or merge an existing presentation slide-by-slide. Instead: Read all five presentations thoroughly. Understand each member's actual contribution. Extract the strongest explanations, diagrams, screenshots, and visuals from each presentation. Create one unified presentation with a consistent design and logical flow. The final presentation should represent the entire project, while ensuring every member's individual contribution is accurately represented. Theme Design the presentation with a: Bright, modern light theme White background Soft blue/green accent colours Professional icons Rounded cards Modern typography Minimal but attractive animations Consistent layouts Plenty of whitespace High-quality visuals The presentation should look like it was professionally designed for a university Capstone defense. Overall Structure Title Agenda Problem Statement & Motivation System Overview 5–14. Main Technical Content (10 slides) Conclusion Q&A Slide Allocation Every member must receive exactly 2 technical slides. At the bottom of every content slide include Presented by: [Member Name] VERY IMPORTANT Do NOT simply copy anyone's presentation. Instead: Compare all five presentations. Take the strongest explanation. Merge duplicated information. Preserve every important contribution. Improve wording where necessary. Produce one polished presentation. The presentation should summarize the entire project, not five separate presentations. Preserve Individual Contributions Do NOT redistribute ownership incorrectly. Use the uploaded presentations to identify each member's real work. Mrigendra Man Baidhya This section should be based on my individual presentation. Include: Slide 1 – Video Processing & Data Pipeline Project objective Why preprocessing is necessary 4 FPS downsampling Two-stage face cropping Temporal smoothing End-to-end data pipeline Data aggregation workflow Why aggregation is performed before visualization System architecture from upload to report generation Slide 2 – Visualization & Local LLM Include Dashboard generation Student and classroom visualizations Data aggregation engine Local Ollama integration Qwen2.5 1.5B Prompt engineering AI-generated teacher summaries Rule-based fallback Why local inference instead of cloud APIs Privacy-first architecture LLM timeout handling Engineering challenges Future improvements Also include challenge/solution boxes such as Ollama timeout handling High-resolution processing bottlenecks Chart rendering issues Do not replace this section with head pose estimation, as that belongs to another member. Sahel Shrestha Build these slides from Sahel's presentation. Include Video preprocessing rationale solvePnP Rodrigues Transform Head pose estimation Pitch/Yaw calculations Threshold selection ±5° tolerance Rolling average Background threading FFmpeg pipeline Two-stage face detection Design decisions Technical challenges Engineering solutions Also use the appendix explanations where useful to explain why MediaPipe, solvePnP, and 4.28 FPS were chosen. Samyak Adhikari Use Samyak's presentation. Include EAR calculation EAR formula Attention thresholds Rule-based classification Streamlit frontend CSS styling Session management User workflow Upload process Reports pages Frontend strengths Weaknesses Future improvements Do not only show screenshots. Explain why each page exists and how the frontend supports teachers. Spandan Acharya Use Spandan's presentation. Include FaceTracker DeepSORT Kalman Filter Hungarian Algorithm Appearance embeddings Identity preservation Occlusion handling Tracking parameters QA methodology Test cases Defect tracking Regression testing Results Future work Include his challenge slides because they are excellent. Sareen Adhikari Use Sareen's presentation. Include SQLite schema Anonymous storage Validation methodology Precision Recall F1-score Cohen's Kappa Fleiss' Kappa Session reliability Dashboard metrics Database design decisions Validation challenges Solutions Dashboard components Also include the dashboard visualizations discussed in her slides. Every Member Section Must Include Each two-slide section should contain: Objective Technical implementation Workflow Design decisions Challenges encountered Solutions implemented Key strengths Future improvements (if applicable) The audience should understand not only what was built, but also why, how, and what engineering decisions were made. Visual Improvements Replace long paragraphs with: Architecture diagrams Pipelines Flowcharts Icons SmartArt Process diagrams Tables Timeline graphics Dashboard screenshots Comparison boxes Avoid walls of text. Technical Depth This presentation is for a Capstone II defense. Every slide should contain enough technical detail for examiners to ask follow-up questions. Do not oversimplify. Explain: Why the technology was chosen Alternatives considered Engineering trade-offs Design decisions Challenges Limitations Final Deliverables Produce: A completely redesigned PowerPoint (.pptx) Bright modern light theme Exactly 2 content slides per member Presenter name in the footer of each slide Speaker notes for every slide A presentation that accurately summarizes all five uploaded presentations while preserving each member's real contribution and creating a cohesive, professional Capstone II defense.
Presentation overview
This community presentation was shared by Mrigendra Baidhya as a complete 17-slide example. I will provide five individual Capstone II defense presentations. Your task is to create a completely new presentation from scratch. Do NOT modify or merge an existing presentat… 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.
