--:--:-- CET
πŸ“… Thursday, June 18, 2026 πŸ“ ISU, Strasbourg ⏱ 14:00 - 16:00

Lab: Final Polish,
Deploy, and Rehearse

The last working session before finals. Ship it, showcase it, and rehearse your story.

9
Day
PM
Session
2h
Duration

Dr. Anwar Sounny · AS26: AI-Powered Earth Observation

Final Sprint This Is It
🏁

Last Session Before Finals

Tomorrow morning, you present. Everything you do in the next two hours directly impacts your grade and your showcase portfolio.

⚠️ Reality Check
No new features from this point. The only code you write now is bug fixes, cleanup, and polish. Feature creep in the final hours has sunk more projects than bad code ever has.
πŸ’‘ Mindset
Think of this session as three sprints: Deploy (30 min), Showcase (30 min), Rehearse (60 min). Work the clock.
Final Sprint Priority Stack

If time is short, work top to bottom. Never skip #1 for #3.

#1
App Works + Deployed
Live on GitHub Pages. Core features functional. No crashes.
#2
Presentation Ready
Slides done. Demo flow rehearsed. Timing under 10 min.
#3
Showcase Complete
All fields filled. Video uploaded. Logo and screenshot added.
πŸ’‘ The Golden Rule
A simple app that works and is well-presented will always score higher than a complex app that crashes during the demo.
Deployment Automated Pipeline: Final Verification

With our Enterprise CI/CD pipeline in place, your app is automatically deployed to GitHub Pages when you push to main. This is your final check to verify the live URL.

  1. Push your latest code to the main branch. This triggers your GitHub Action pipeline.
  2. Go to the Actions tab in your repository. Ensure both your tests/linting jobs and deployment job pass successfully.
  3. Fix any pipeline failures. If your build fails because of a security vulnerability or linting error, you must fix it and push again.
  4. Open the live URL in an incognito/private window. This tests what a fresh visitor sees, not your cached version.
  5. Test every feature from the live URL. Click every button. Submit every form. Load every map layer.
🚨 Critical
The demo URL you present tomorrow must be the automated GitHub Pages URL, not localhost. If the pipeline is blocked by security scans, your code is NOT deployed. Fix it now.
Deployment Deployment Checklist

Go through every item. Check them off as you complete each one.

  • API keys are working (Sentinel Hub, OpenAI, Mapbox, etc.)
  • Test on phone (responsive layout, touch interactions)
  • Test on tablet (medium breakpoint, map sizing)
  • Test on laptop (Chrome, Firefox, or Safari)
  • Remove debug code (console.log, alert, test data)
  • Update README.md with project name, description, and usage
  • Add a favicon (16x16 or 32x32 PNG in the root folder)
  • Set a proper <title> tag (not "Untitled" or "React App")
  • All image paths resolve (no broken images, no 404s)
  • No hardcoded localhost URLs remaining in the code
Deployment Code Cleanup: Final Pass

Before your final commit, do a search-and-destroy pass through your codebase. Here is what to look for:

// ============================================
// FINAL DEPLOYMENT CLEANUP CHECKLIST
// ============================================

// 1. Set DEBUG flag to false
const DEBUG = false;  // Was: true

// 2. Remove unused console.log() calls
//    Search your project: Ctrl+Shift+F → "console.log"

// 3. Verify all API endpoints are correct
const API_BASE = "https://services.sentinel-hub.com";
// NOT: "http://localhost:3000/api"

// 4. Check all image paths resolve
//    Relative paths: "./images/logo.png"
//    NOT: "C:\\Users\\you\\Desktop\\logo.png"

// 5. Test offline behavior gracefully
if (!navigator.onLine) {
  showMessage("Please check your internet connection.");
}
⚠️ Pro Tip
Use your editor's global search (Ctrl+Shift+F) to find all instances of console.log, localhost, TODO, and FIXME. Remove or resolve each one.
Deployment Run a Lighthouse Audit

Lighthouse is a free tool built into Chrome DevTools that audits your app for performance, accessibility, best practices, and SEO. Running it takes 30 seconds and can reveal issues you would otherwise miss.

  1. Open your live GitHub Pages URL in Chrome.
  2. Press F12 to open DevTools, then click the Lighthouse tab.
  3. Select categories: Performance, Accessibility, Best Practices.
  4. Click "Analyze page load" and wait ~15 seconds.
  5. Review the scores and fix any critical issues (red items).
90+
Performance Target
90+
Accessibility Target
90+
Best Practices Target
πŸ’‘ Quick Wins
Add alt text to images, compress large images, and add meta description tags. These three fixes alone can boost your scores by 10-20 points.
Quiz Deployment Knowledge Check
1. Why should you test your GitHub Pages site in an incognito window?
Incognito mode loads pages faster.
It simulates a fresh visitor without cached assets, cookies, or saved state.
GitHub Pages only works in incognito mode.
2. What does a Lighthouse audit measure?
How many lines of JavaScript your app has.
Whether your API keys are valid.
Performance, accessibility, best practices, and SEO of your web page.
3. Which of these should you remove before your final deployment?
Your README.md file.
console.log() statements, TODO comments, and debug flags set to true.
Your CSS stylesheet.
Showcase Project Showcase Submission

Your project will be featured on the AS26 Project Showcase page. This is your public portfolio entry: future employers, ISU alumni, and the broader space community will see it.

  1. Navigate to the showcase portal link above.
  2. Log in with your ISU Google account.
  3. Click "Submit Project" and fill in all required fields (see next slide).
  4. Review your entry before submitting. You can edit until the deadline.
πŸ’‘ Why This Matters
Your showcase entry is part of your grade. It is also the artifact that lives on after the course ends. Treat it like a professional portfolio piece.
Showcase Required Submission Fields

Fill in every field. Incomplete submissions will lose points. Here is what you need to prepare:

FieldWhat to Provide
Project NameA memorable, descriptive name
Team MembersFull names of all contributors
Description2-3 sentences: clear, compelling, jargon-free
LogoSquare image (create with Canva or AI tools)
ScreenshotA high-quality screenshot of your app in action
YouTube Video60-second commercial (record with OBS or Loom)
Live App URLYour GitHub Pages URL
Pitch DeckLink to Google Slides or Canva presentation
Investor InfoMarket size, business model, competitive advantage
⚠️ Don't Have a Logo?
Open Canva or use an AI image generator. A simple logo with your project initials on a gradient background takes 5 minutes.
Showcase 60-Second Video: Tips

Your YouTube "commercial" should follow a tight Problem → Solution → Demo format. Here is a breakdown:

15s
The Problem
15s
Your Solution
25s
Live Demo
5s
Call to Action

Recording Tools

  • OBS Studio (free, open source): Screen + webcam recording with full control.
  • Loom (free tier): One-click screen recording, auto-uploads to the cloud.
  • Zoom: Share screen and record locally. Quick and familiar.

Production Tips

  • Record in a quiet room. Background noise kills credibility.
  • Use a script. Read it aloud twice before recording.
  • Show the app doing something. Static screenshots are not a demo.
  • Upload as Unlisted on YouTube if you prefer privacy.
Rehearsal Structured Rehearsal Plan

You have roughly 60 minutes for rehearsal. Use this structured three-round approach:

R1
Solo Run-through
Present to yourself. Time it. Target 8-9 minutes to leave buffer.
R2
Partner Feedback
Present to a classmate. Ask: "What was unclear? Where did I lose you?"
R3
Final Refinement
Incorporate feedback. Cut anything that didn't land. Polish transitions.
πŸ’‘ Rehearsal Science
Research on oral presentation skills in higher education consistently shows that structured practice and feedback are among the strongest predictors of presentation quality, often outweighing content depth or slide design alone.1

What to Rehearse

  • Your opening: The first 30 seconds set the tone. Nail it.
  • The live demo: Practice the exact click sequence. Have a backup plan if the API is slow.
  • Your closing: End with impact, not "um, that's it." Prepare a strong final sentence.
Rehearsal Common Last-Minute Pitfalls

These are the issues that trip students up every year. Check each one now, not tomorrow morning.

PitfallFix
Slide text too smallMinimum 24px for body text, 36px for headings. Test from the back of the room.
Demo crashes from live URLTest the GitHub Pages URL right now. Do not assume it works because localhost does.
Too much content, not enough timeCut slides ruthlessly. 1 slide per minute is the maximum pace.
No backup if internet dropsTake screenshots or a screen recording of your demo flow as a fallback.
Reading from slidesSlides are visual aids, not scripts. Speak to the audience, not the screen.
No clear problem statementLead with "Why does this matter?" before showing what you built.
🚨 The #1 Killer
Running over time. If you have 10 minutes and you use 12, the evaluators will cut you off. Practice with a timer. Every time.
Rehearsal Tomorrow's Schedule: Finals Day

Friday, June 19, 2026 is presentation day. Here is the format:

TimeActivity
10:00Final presentations begin
Per team10 min presentation + 5 min Q&A
~12:30Wrap-up, awards, and closing

Evaluation Criteria

25%
Innovation
25%
Technical Execution
20%
Presentation Quality
20%
Impact Potential
10%
User Experience
🎯 What Evaluators Look For
Innovation: Is this a novel approach to a real problem?
Technical: Does the code work? Is the AI integration effective?
Presentation: Was the story clear and well-timed?
Impact: Could this be used by real people?
UX: Is the app intuitive and well-designed?
Summary What You've Accomplished in 9 Days

Take a moment to appreciate how far you have come. Nine days ago, most of you had never touched satellite data or built an AI-powered application.

Days 1-2
Foundations: Orientation, AI fundamentals, and the web platform.
Days 3-4
Data: Maps, satellite APIs (Sentinel Hub, Copernicus).
Day 5
Innovation: Factory 2026 Innovation Day pitch.
Days 6-8
Build Sprint: AI integration, feature development, iteration.
Day 9
Ship: Final polish, deploy, and rehearse.
Day 10
Showcase: Final presentations and celebration.
πŸŽ“ Summary of Big Ideas
1. You built an AI-powered web application from scratch.
2. You integrated real satellite data from operational Earth observation missions.
3. You pitched to real investors at Factory 2026.
4. You deployed a live application accessible to anyone on the internet.
Summary Final Words
πŸš€

You Are Ready

Tomorrow is not a test of what you memorized. It is a demonstration of what you can build, explain, and defend. You have done the work. Now tell the story.

"The best way to predict the future is to invent it."

Alan Kay, Xerox PARC, 1971

🎯 Tonight's To-Do List
1. Get a good night's sleep.
2. Arrive by 9:30 AM to set up and test the projector.
3. Have your demo URL bookmarked and ready.
4. Breathe. You have earned this.
Glossary Key Terms
Deployment
The process of publishing your application so that it is accessible to users via a public URL. For this course, we use GitHub Pages for static site hosting.
Favicon
A small icon (typically 16x16 or 32x32 pixels) displayed in the browser tab next to the page title. Adds professionalism and brand identity.
Lighthouse
An open-source tool by Google built into Chrome DevTools. It audits web pages for performance, accessibility, best practices, and SEO, returning a score from 0 to 100 per category.
OBS Studio
Open Broadcaster Software. A free, open-source tool for screen recording and live streaming, widely used for demo videos and educational content.
README.md
A Markdown file in the root of a repository that describes the project: what it does, how to use it, and how to contribute. GitHub renders it automatically on the repo page.
Canva
A web-based graphic design tool for creating logos, presentations, social media graphics, and more. Free tier is sufficient for most project needs.
Loom
A screen recording tool that records your screen, webcam, and microphone simultaneously. Generates a shareable link automatically after recording.
GitHub Pages
A free static site hosting service from GitHub. Serves HTML, CSS, and JavaScript directly from a repository branch, accessible at username.github.io/repo-name.

References
1 van Ginkel, S., Gulikers, J., Biemans, H., & Mulder, M. (2017). Fostering oral presentation performance: Does the quality of feedback differ when provided by the teacher, peers or peers guided by tutor? Assessment & Evaluation in Higher Education, 42(6), 953-966. DOI: 10.1080/02602938.2016.1212984
2 De Grez, L., Valcke, M., & Roozen, I. (2009). The impact of goal orientation, self-reflection and personal characteristics on the acquisition of oral presentation skills. European Journal of Psychology of Education, 24(3), 293-306. DOI: 10.1007/BF03174762

1 / 17
🌟 Pioneer Profile
πŸ‘€

Guy Kawasaki

Pitch and Evangelism Expert

Guy Kawasaki was Apple's chief evangelist and author of 'The Art of the Start.' His 10/20/30 rule for presentations (10 slides, 20 minutes, 30-point font) became the gold standard for startup pitches. He proved that great technology needs great storytelling to succeed.

🌍 Local to Global

Global Data, Local Impact

Applying EO to Community Challenges

Earth Observation provides a macroscopic view of environmental trends, but its true power lies in downscaling this data to affect local policy and design, such as urban planning and sustainable workplaces.

πŸ“
Texas Connection: In Texas, EO data is used to monitor the Edwards Aquifer depletion and track the expansion of urban heat islands across the Dallas-Fort Worth metroplex.
πŸ—ΊοΈ
πŸ€” Geographic Inquiry

Regional Decisions Scenario

Scenario: Sustainable Workspace Siting

Your startup needs to establish a new hybrid work hub. You must balance employee commute times, environmental impact (using the IPAT equation), and existing green infrastructure.

Your Task:

  • Identify 3 potential sites using EO vegetation indices.
  • Calculate the estimated carbon footprint of hybrid commuting.
  • Propose a Placemaking strategy for the hub.
πŸ“š Summary

Big Ideas & Glossary

Summary of Big Ideas

  • Data is only as valuable as its application.
  • Space technology has direct terrestrial benefits.

Glossary of Terms

Earth Observation
Gathering information about Earth via remote sensing.
πŸ“ Knowledge Check

Auto-Graded Quiz

What is the primary benefit of remote sensing in sustainability?
A
It replaces the need for local governance.
B
It provides continuous, objective data over large, inaccessible areas.
C
It lowers the cost of launching rockets.
βœ… Correct! Remote sensing allows for consistent monitoring of remote regions without expensive on-the-ground surveys.
❌ Incorrect. The right answer was B. Remote sensing allows for consistent monitoring of remote regions without expensive on-the-ground surveys.

πŸ“ Daily Reflection

What was your biggest takeaway from this session, and how does it apply to the TERRA project? Write your response below. Your instructor will review this to track your progress.