Loading...
Community presentation
Create a high-impact 6-slide Smart India Hackathon 2026 presentation for our project: DRISHTI-EDGE Autonomous Edge Intelligence for Disaster Reconnaissance Problem Statement ID:…
Create your own version
Use this visual direction as inspiration for a new Presenton deck.
Use this designCreator prompt
Create a high-impact 6-slide Smart India Hackathon 2026 presentation for our project: DRISHTI-EDGE Autonomous Edge Intelligence for Disaster Reconnaissance Problem Statement ID: 26177 Theme: Robotics and Drones IMPORTANT: The attached/current deck contains the approved technical content. DO NOT invent new technical claims, features, performance numbers, accuracy values, datasets, partnerships, or results that are not present in the source material. The goal is NOT to make a conventional corporate presentation. Create a presentation that looks like a premium deep-tech / defense-tech / disaster-response product pitch and communicates the solution visually. ================================================== CORE DESIGN PHILOSOPHY ================================================== The current version is too text-heavy. Do NOT simply convert paragraphs into bullet points. Every slide must have a strong VISUAL STORY. Target approximately: - 60–70% visual content - 30–40% text - very little paragraph text - maximum 3–5 short text blocks per slide - use diagrams, system architecture, maps, icons, process flows, UI mockups, sensor illustrations, drone illustrations, and visual hierarchy The jury should understand the core idea even if they only glance at the slides. Think: "deep-tech startup pitch + disaster command center + autonomous drone system" NOT: "college project report" ================================================== VISUAL STYLE ================================================== Use a sophisticated disaster-response / aerospace / AI aesthetic. Color palette: - deep navy / midnight blue - white / off-white - electric blue - restrained orange/red for danger, alerts and priority - subtle green only for safe/confirmed states Use: - dark technical backgrounds on selected slides - clean white backgrounds where readability is more important - glowing data paths - radar/grid elements - satellite-map textures - drone silhouettes - thermal-camera style imagery - computer-vision bounding boxes - geospatial overlays - incident markers - command-center UI elements - subtle circuit/AI patterns Avoid: - generic corporate stock photos - childish illustrations - excessive gradients - excessive rounded cards - random decorative icons - clip-art - huge paragraphs - walls of bullet points - generic "AI brain" stock graphics The design should feel engineered, credible and technically sophisticated. ================================================== SLIDE 1 — THE MISSION ================================================== Title: DRISHTI-EDGE Subtitle: Autonomous Edge Intelligence for Disaster Reconnaissance Create a cinematic hero slide. VISUAL: Show a disaster environment from an aerial drone perspective. The drone should be observing a damaged/flooded/unstable environment. Overlay: - RGB camera detection - thermal detection - survivor bounding box - hazard marker - GPS coordinates - P1/P2/P3 incident indicators Make the visual communicate: DRONE → SENSE → UNDERSTAND → PRIORITIZE → RESCUE Do NOT fill the slide with the problem statement. Put only the essential metadata: SIH 2026 Problem Statement ID: 26177 Theme: Robotics and Drones Team name / Team ID placeholders Use the tagline prominently: "WHEN THE NETWORK FAILS, RESCUE INTELLIGENCE SHOULDN'T." ================================================== SLIDE 2 — THE PROBLEM → THE BREAKTHROUGH ================================================== Title: FROM RAW VIDEO TO RESCUE INTELLIGENCE Instead of bullets, create a visual before/after comparison. LEFT: Traditional disaster reconnaissance DRONE VIDEO ↓ NETWORK / BACKHAUL ↓ MANUAL REVIEW ↓ DELAY ↓ RESPONDER EXPOSURE Show this as a red/orange failure pipeline. RIGHT: DRISHTI-EDGE RGB + LWIR + IMU + GNSS ↓ ON-DEVICE EDGE AI ↓ MULTIMODAL FUSION ↓ GEO-LOCALIZATION ↓ RISK / SEVERITY ↓ PRIORITIZED INCIDENTS Show this as a clean blue/green intelligence pipeline. At the bottom make the key differentiation visually dominant: "NOT JUST OBJECT DETECTION. ACTIONABLE RESCUE INTELLIGENCE." Use a visual transformation: RAW SENSOR DATA → STRUCTURED RESCUE DECISION ================================================== SLIDE 3 — TECHNICAL ARCHITECTURE ================================================== Title: FROM SENSING TO RESCUE DECISION THIS SHOULD BE THE MOST TECHNICAL AND MOST VISUAL SLIDE. Create a professional system architecture diagram. Architecture: DRISHTI-EDGE ┌───────────────────────────────────────────────┐ │ FIELD SENSING │ │ │ │ Drone | RGB | LWIR | IMU | GNSS │ └──────────────────────┬────────────────────────┘ ↓ ┌───────────────────────────────────────────────┐ │ EDGE PERCEPTION │ │ │ │ Lightweight CV | TensorRT | Detection │ │ Confidence Estimation │ └──────────────────────┬────────────────────────┘ ↓ ┌───────────────────────────────────────────────┐ │ MULTIMODAL FUSION │ │ │ │ RGB + Thermal + Inertial + Position │ └──────────────────────┬────────────────────────┘ ↓ ┌───────────────────────────────────────────────┐ │ SPATIAL INTELLIGENCE │ │ │ │ Survivor coordinates | Hazard coordinates │ │ Hazard boundaries | Spatial-temporal context │ └──────────────────────┬────────────────────────┘ ↓ ┌───────────────────────────────────────────────┐ │ RISK / SEVERITY ENGINE │ │ │ │ Severity + accessibility + urgency + │ │ nearby hazards + confidence │ └──────────────────────┬────────────────────────┘ ↓ P1 / P2 / P3 PRIORITY ↓ ┌───────────────────────────────────────────────┐ │ INCIDENT COMMAND │ │ │ │ Geo-spatial map | Incident queue │ │ Survivor cards | Hazard cards | Telemetry │ └───────────────────────────────────────────────┘ Use icons and visual connectors rather than paragraphs. IMPORTANT: Visually highlight the OFFLINE-FIRST architecture. Show a broken/disconnected network/cloud icon above the system. Then show: NETWORK LOST ↓ LOCAL SENSORS ↓ EDGE AI ↓ DETECTION ↓ GEO-TAGGING ↓ RISK SCORING ↓ LOCAL STORAGE Then: NETWORK RESTORED ↓ PRIORITY-FIRST SYNCHRONIZATION This is one of our strongest differentiators. Make it visually prominent. ================================================== SLIDE 4 — FEASIBILITY + MVP ================================================== Title: AMBITION IS LARGE. THE MVP IS REALISTIC. Do NOT use a wall of feasibility bullets. Create a 4-layer visual: TECHNOLOGY ↓ OPERATION ↓ AI / DATA ↓ SCALABILITY For each layer show: WHAT WE CAN DO NOW + CHALLENGE + MITIGATION Use concise visual labels. Then create a prominent "SIH MVP" box: AUTONOMOUS WAYPOINT RECONNAISSANCE + RGB + THERMAL CAPTURE + EDGE INFERENCE + GEO-TAGGED DETECTION + OFFLINE LOCAL LOGGING + INCIDENT DASHBOARD + RECONNECTION SYNCHRONIZATION At the bottom show a roadmap: MVP → FIELD-READY PLATFORM → MULTI-DRONE COORDINATION → DISASTER-RESPONSE NETWORK Clearly separate: MVP from PLANNED / FUTURE Do NOT make future features look already implemented. ================================================== SLIDE 5 — IMPACT ================================================== Title: FROM RAW SCENE TO PRIORITIZED ACTION Make this slide extremely visual. Create a before → after transformation. LEFT: DISASTER SCENE Aerial image showing: - survivors - damaged structures - flood/fire/debris/hazards Then show raw drone video / sensor feed. CENTER: DRISHTI-EDGE Show the AI processing pipeline: DETECT → FUSE → GEO-LOCATE → ASSESS RISK → PRIORITIZE RIGHT: RESPONDER COMMAND VIEW Show a realistic dashboard mockup containing: P1 — SURVIVOR + HIGH HAZARD P2 — SURVIVOR P3 — HAZARD / MONITOR Map pins and incident cards. Then communicate the benefits using 4 large visual keywords: FASTER AWARENESS NETWORK RESILIENCE SAFER RESPONDERS LOWER COGNITIVE LOAD End with: SEE FASTER → UNDERSTAND BETTER → PRIORITIZE SMARTER → RESCUE SAFER ================================================== SLIDE 6 — WHY THIS ARCHITECTURE ================================================== Title: WHY DRISHTI-EDGE IS DIFFERENT Do NOT leave this as a blank references slide. Create a visual comparison: CONVENTIONAL DRONE Drone → Video → Human interpretation vs. DRISHTI-EDGE Drone ↓ Multimodal sensing ↓ Edge intelligence ↓ Geo-localized incidents ↓ Risk-aware prioritization ↓ Responder decision support Then create a small "DESIGN PRINCIPLES" area: OFFLINE-FIRST MULTIMODAL FUSION GEO-LOCALIZED INTELLIGENCE RISK-AWARE TRIAGE HUMAN-IN-THE-LOOP Put research/reference sources in a clean, small footer section. ================================================== VISUAL ASSET REQUIREMENTS ================================================== Generate or select appropriate visuals for the deck. Prioritize: 1. realistic autonomous disaster-response drone 2. aerial disaster reconnaissance 3. thermal-camera visualization 4. computer vision detection overlays 5. geospatial disaster map 6. emergency command dashboard 7. sensor-fusion diagram 8. edge AI / onboard computing illustration 9. offline/network failure visualization 10. incident-priority interface VISUALS MUST SUPPORT THE TECHNICAL STORY. Do not add images merely to decorate empty space. ================================================== TYPOGRAPHY ================================================== Use a modern technical sans-serif font. Use: - extremely large slide titles - short powerful subheadings - bold numerical / priority labels - small technical annotations Avoid serif-heavy academic styling. No paragraph should be longer than 2 lines wherever possible. ================================================== LAYOUT RULES ================================================== Every slide should have ONE dominant visual idea. Use: - asymmetrical layouts - full-bleed visuals - large diagrams - visual pipelines - split-screen comparisons - architectural diagrams - dashboard mockups - large callout statements Avoid repeating the same layout on every slide. Do not make every slide: TITLE + 5 BULLETS + EMPTY SPACE. Each slide must feel intentionally designed. ================================================== CONTENT FIDELITY ================================================== Use the source deck as the authoritative source for project claims. Preserve the technical terminology: - RGB - LWIR - IMU - GNSS - TensorRT - edge inference - multimodal fusion - geo-localization - risk/severity engine - P1/P2/P3 - offline-first - local storage - synchronization after reconnection - human-in-the-loop Do not invent: - accuracy percentages - latency numbers - datasets - trained model names - deployment results - number of drones - field-test results - partnerships - funding - patents - performance benchmarks unless they are explicitly present in the source material. ================================================== FINAL QUALITY BAR ================================================== The finished presentation should look like something presented by a serious deep-tech disaster-response startup / research lab at a national-level hackathon. A jury member should be able to understand: 1. WHAT is the problem? 2. WHY do conventional drone systems fail? 3. WHAT exactly does DRISHTI-EDGE do? 4. HOW does the architecture work? 5. WHY is offline edge intelligence important? 6. WHY is the MVP feasible? 7. WHAT impact does it create? without reading dense paragraphs. Make it: VISUAL TECHNICAL CREDIBLE MEMORABLE JURY-FRIENDLY PREMIUM The presentation should feel like: "THIS TEAM HAS BUILT A REAL SYSTEM" rather than: "THIS TEAM HAS WRITTEN A PROJECT REPORT."
Presentation overview
This community presentation was shared by Aryan Nagannavar as a complete 6-slide example. Create a high-impact 6-slide Smart India Hackathon 2026 presentation for our project: DRISHTI-EDGE Autonomous Edge Intelligence for Disaster Reconnaissance Problem Statement ID:… 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.
