Build It: Your Boarding Pass Page
Module 1 · Day 1 — Learn the Loop

Build It: Your Boarding Pass Page

Run the loop yourself, iterate at least twice more, and save your first project with the naming convention you'll use all week.

🛠️ Your Turn: Build v1

Open Gemini, turn on Canvas, and fill in the prompt template from the last lesson with your own details. This is your personal boarding-pass profile page — something you could show a new classmate in ten seconds.

💻 Code Lab: Build Your v1

Fill in every blank with something specific to you:

Build a boarding-pass-style webpage that shows [your name],
[your home airport or city], [a place you'd love to fly to],
and [a fun fact about you], for someone meeting me for the
first time, styled like [pick a vibe — retro airline, modern
minimalist, playful cartoon, whatever fits you]. Make
[something specific] happen when I [click/hover/type].

Send it. Watch the preview build. Then run the loop:

  1. Test — click everything, read every word, check it on both a wide and narrow browser window
  2. Refine — pick the single most annoying thing and ask Gemini to fix just that
  3. Repeat — test again

Aim for at least two full refine loops before you call this “v1 done.”

⚠️ Common Pitfall: Fixing Everything in One Refine Message

If you list five things you want changed in a single refine prompt, Gemini might only catch three of them — and now you can’t tell which two got missed. Refine one or two related things at a time, check the result, then move to the next. Slower feels safer, but it’s actually faster: you never have to untangle a broken batch of changes.


☕ Break (10 min)

Stretch your legs. Look at someone else’s screen if you want inspiration — no copying required, just ideas.


🔄 Keep Iterating

Come back and run the loop at least two more times. Some directions worth trying:

  • Add a background gradient or texture that matches your vibe
  • Add a second small detail (a “frequent flyer status,” a favorite airline, a travel quote)
  • Fix anything that looked wrong on a smaller screen
  • Ask Gemini to explain what one part of the code does — you’re allowed to be curious

There’s no finish line today. The goal is comfort with the loop, not a “complete” product.


💾 Save & Share

Naming Convention

Every file you save this week follows the same pattern, so there’s a visible trail of your progress by Friday:

name_dayX_vY.html

Example: maria_day1_v1.html — if Maria comes back to this same project tomorrow and iterates on it, the next save becomes maria_day2_v2.html. The version number climbs; it never resets unless you start a brand-new project.

Iterating never overwrites. Always bump the version number so today’s v1 stays saved even after you build v2.

Where It Goes

Save (or export) your file into the shared Google Drive folder, in the Day 1 subfolder. If you’re one of the four Software Engineering majors and want extra version-control practice, you can instead commit today’s file to the shared GitHub repo — everyone else uses Drive, and that’s just as good.

Quick Share Round

We’ll go around the room — 15 seconds each. Just say what your page shows and one thing you’re proud of. No pressure to be finished.

🧠 Knowledge Check

You already saved maria_day1_v1.html yesterday. Today you open that same project and make more changes. What should the new filename be?

Reveal Answer & Explanation

maria_day1_v2.html — same day, next version number.

The day number only changes when you’re actually working on a different day’s session; the version number climbs every time you save a new iteration of the same project, no matter which day you’re in. That way anyone looking at the Drive folder can see the exact trail of every change you made, in order.


🚀 Stretch Challenge (optional)

Already happy with your v1 and have extra time? Try one of these:

  • Add a CSS hover animation to one element
  • Add a background gradient
  • Make the layout adjust on a smaller screen using a media query

⏭️ Up Next

Tomorrow you’ll add a new lens before you even open Gemini: thinking like a product manager, and three simple UX habits that make anything you build easier to use.