Day 02 of 10
Build the landing page
Goal: Turn yesterday’s words into one simple page that opens and works on your computer. (~60 min)
Now you finally get something on screen. The goal today is not a beautiful launch. The goal is a working first version. One page. One goal. One action. If it feels plain, that is fine. Plain and working beats fancy and half-broken.
What to do
Create the project folder and open it in Cursor
On your Desktop (or anywhere easy to find), right-click → New Folder → name it something like "my-landing-page". Then open Cursor, click File → Open Folder, and select that folder. You should now see an empty sidebar on the left — that is your project. This is where all your files will live. If you prefer to keep things simpler, you can also just use Claude at claude.ai in your browser and paste the code it gives you into a plain text file saved as "index.html". You do not need Cursor if you go that route — just make sure to save the file with the .html extension, not .txt.
Ask AI to scaffold the page
Ask Codex or Claude Code to create a single-page HTML landing page with a hero, benefits, proof, FAQ, and CTA.
Copy this Day 2 build prompt into Codex or Claude Code
Paste this after you open your project folder. Let the AI build the first version before you start tweaking small details.
I am a non-technical beginner building a simple validation landing page.
Please create a one-page landing page for this idea: [PASTE IDEA].
Use this copy: [PASTE COPY BLOCK FROM DAY 1].
Requirements:
- One page only
- Sections: hero, benefits, proof, FAQ, final CTA
- Clean, simple, beginner-friendly layout
- Mobile-friendly
- Use the simplest setup already in this project
- Do not add login, pricing, dashboards, or extra pages
Important:
- Explain what you are doing in plain English
- Tell me which file(s) you created or changed
- Tell me exactly how to run or preview the page when you are done
- If you are unsure, choose the simplest optionAdd the core sections
Make sure the page includes the headline, benefits, social proof, FAQ, and final CTA.
Run the page locally
How you preview the page depends on what the AI built. There are two common situations: Situation A — The AI created a plain HTML file (most common for beginners): Open your project folder, find the file called "index.html", and double-click it. It opens straight in your browser. That is your local preview. If it looks wrong, that is fine — you will fix it in the next steps. Situation B — The AI created a Next.js or React project: In Cursor, click View → Terminal to open a terminal panel at the bottom. Type: npm install and press Enter. Wait for it to finish (this can take a minute). Then type: npm run dev and press Enter. Then open your browser and go to http://localhost:3000. Your page should appear there. Not sure which one you have? Look at your project folder. If you see only a file called "index.html" and maybe a CSS file — that is Situation A. If you see a folder called "src" or files called "package.json" — that is Situation B. If still unsure, paste the list of files you see into Claude and ask which situation you are in.
Check mobile layout
Use your browser or dev tools to make sure the page still reads well on a small screen.
Save a clean version with GitHub Desktop
This is your safety checkpoint. If anything breaks tomorrow, you can come back to exactly this working version. 1. Open GitHub Desktop (you installed this at the end of Day 1). 2. Click File → Add Local Repository. 3. Click Choose and select your project folder. 4. If GitHub Desktop says "This directory does not appear to be a Git repository" — click "create a repository" and follow the prompts. Click Initialize Repository when asked. 5. You should now see a list of your files on the left side. They will be highlighted green — that means they are new and ready to save. 6. At the bottom left, in the box that says "Summary (required)", type: working page before email setup 7. Click the blue "Commit to main" button. 8. Done. Your checkpoint is saved. If GitHub Desktop feels too confusing right now, the quickest alternative is to duplicate your project folder: right-click it → Copy → Paste → rename it "my-landing-page-backup". Not as clean as Git, but it protects your work.
Expected result
Your landing page opens locally, the main sections are there, and you have a safe checkpoint before adding more.
Common mistake
Adding extras too early. If the basic page is not working yet, nothing else matters.
What you learned
- Structure comes first. Polish can wait.
- A one-page landing page is much easier to finish than a whole mini-site.
- Most early mistakes show up as soon as you preview the page locally.
Tomorrow
Day 3 - you add a real waitlist form. By the end you will know the form actually captures signups.