From Zero to Your First Live Website: A Cursor + Vercel Adventure for Complete Beginners
I used to think deploying a website meant being some hoodie-wearing genius who speaks in mysterious commands and hasn't seen sunlight in months. That you needed a computer science degree, years of practice, and some secret handshake with the tech gods.
I was completely wrong.
Now I spin up sites in minutes. And I want you to feel that too.
This is the article I wish someone had written for me when I was staring at a blank screen, wondering if I was "technical enough" to build something real. Spoiler: you are. And by the end of this article, you'll have proof—a live URL you can share with anyone.
No terminal required. No cryptic commands. Just clicking, typing plain English, and watching magic happen.
Who this is for (and who it's not for)
✅ This guide is for you if:
- You've never built a website but want to
- You've tried tutorials before and felt lost after step 3
- You think you're "not technical enough" (you're wrong, but I get it)
- You want something live on the internet TODAY, not "someday"
- You learn better with hand-holding than with documentation dumps
⏭️ This might not be for you if:
- You already deploy sites regularly (you'll be bored)
- You want deep theory before practice (we're doing it backwards here)
- You're looking for enterprise architecture guidance (come back later)
What tech you're secretly learning
🎓 By the end of this article, you'll have hands-on experience with:
HTML & CSS (web structure and styling) • Git & GitHub (version control) • Vercel deployment (CI/CD and hosting) • AI-assisted development (prompt engineering)
These are real skills that go on resumes. You're not "cheating"—you're learning the modern way.
Explain it three ways
You know how you can talk to a really smart friend who helps you build LEGO? That's Cursor. And Vercel is like a magic postman who takes what you build and shows it to everyone in the world, instantly. You tell your friend what you want, they help you build it, and the postman delivers it. That's literally it.
This is an end-to-end walkthrough that takes someone with zero development experience and gets them to a deployed web application. The stack is Cursor (AI-powered code editor) + Vercel (serverless deployment platform). ROI: in under 2 hours, complete beginners can have portfolio-quality projects live on the internet, de-risking early-stage product experimentation.
Remember when I said I could "make websites"? This is how. I talk to an AI in plain English inside a special app called Cursor, and it writes the code for me. Then Vercel—it's like Instagram for websites—takes whatever I build and puts it on the internet with one click. The whole thing takes less time than watching a movie. You could genuinely do it tonight if you wanted.
Meet Maya (she's going to be our guide)
👩💼 Maya's story
Maya is a 34-year-old marketing manager. She's always wanted to build her own website but assumed it required "being technical." Last week, a developer friend told her about Cursor and Vercel. Tonight, she's going to try. She's nervous. Her internal voice keeps saying "you're going to mess this up." She's doing it anyway.
We'll check in with Maya throughout this guide. Her journey might look familiar.
The three promises I'm making you
Before we start, let me be crystal clear about what you're getting:
| Promise | What it means in practice |
| --------- | --------------------------- |
| You don't need to "be a developer" | Zero coding background required. If you can type and click, you can do this. |
| You'll have a real live URL | Something you can text to your mom, put on your resume, or show your friends. Not "localhost" nonsense—a real website anyone can visit. |
| I'll walk right beside you | Screenshots descriptions. Copy-paste commands. "If you see this, click that" instructions. No assumptions about what you already know. |
Still nervous? Good. That means you care. Let's channel that energy into building something real.
Before we begin: Your fears are valid (and wrong)
Let me guess what's in your head right now:
😰 "What if I break something?"
You literally cannot break the internet. The worst thing that happens? Your site shows an error, you press "undo," and you're back to normal. Vercel has a rollback button. Cursor has infinite undos. You're safer here than crossing the street.
😰 "I don't understand GitHub"
Neither did I for years. Here's the only thing you need to know: GitHub is a cloud drive for code. Like Google Drive, but for websites. That's it. We'll set it up step-by-step.
😰 "AI coding sounds intimidating"
If you've ever asked ChatGPT a question, you already know how this works. Cursor is just ChatGPT that can directly edit files. You talk to it in plain English. It does the nerdy stuff.
😰 "Am I too late to learn this stuff?"
The best time to plant a tree was 20 years ago. The second best time is now. Also, AI has made this easier than ever. You're not "too late"—you're arriving just as the tools got good.
Deep breath. Let's build.
Chapter 1: Setting Up Your Workspace ⏱️ ~15 min
What we're doing
Before we build anything, we need three things:
- Cursor (the app where you'll work)
- A GitHub account (where your code lives in the cloud)
- A Vercel account (where your website gets published)
All three are free. None require a credit card.
Step 1.1: Download and Install Cursor
Cursor is a code editor powered by AI. Think of it as Microsoft Word, but instead of writing documents, you're building websites—and you have a genius AI assistant who does most of the typing.
Here's what to do:
- Open your browser and go to cursor.com
- Click the big download button
- Run the installer (double-click the file you downloaded)
- Follow the prompts—just keep clicking "Next" or "Continue"
✅ You'll know it worked when...
You see a window that looks like a dark-themed text editor. It might show a "Welcome" tab. If you see something that looks vaguely code-y, you're in the right place.
🔧 Troubleshooting
Mac: If the app doesn't open, drag it from Downloads to your Applications folder first.
Windows: If you see a "Windows protected your PC" popup, click "More info" → "Run anyway." It's safe.
Step 1.2: Create a GitHub Account
GitHub is where your code lives. When you make changes, they get saved to GitHub. When Vercel deploys your site, it pulls from GitHub. Think of it as the central hub.
GitHub explained three ways
Here's what to do:
- Go to github.com
- Click "Sign up" in the top right
- Enter your email, create a password, choose a username
- Complete the puzzle/captcha thing
- Check your email and verify
💡 Username tip
Pick a username you'd be proud to put on a resume. Keep it simple, professional-ish, and easy to remember. sarah-builds-stuff > xXx_c0d3r_420_xXx
🔧 Troubleshooting
If GitHub shows a 404: Double-check you're logged in. Click the profile icon in the top right—if it says "Sign in," you need to log in first.
Step 1.3: Create a Vercel Account
Vercel is the magic button that turns your code into a live website. It's free to start, incredibly powerful, and trusted by huge companies.
💰 Don't worry about money
Vercel's Hobby plan is completely free and designed specifically for personal projects and learning. You can host multiple websites, get unlimited deployments, and even add custom domains—all without paying anything. The paid plans exist for businesses with high traffic. You won't need them for a long time, if ever.
Here's what to do:
- Go to vercel.com
- Click "Sign Up" in the top right
- Important: Choose "Continue with GitHub"
- Authorize Vercel to connect to your GitHub account
🔗 Why connect with GitHub?
This makes everything automatic later. When you push code to GitHub, Vercel will detect it and deploy your site. Zero extra steps. Magic.
🔧 Troubleshooting
If Vercel asks for permissions: Click "Authorize" or "Allow." It needs to see your GitHub repos to deploy them. This is normal and safe.
Chapter 1 Checkpoint
🎉 You just did what most people never do
Seriously. Most people who "want to build a website" never get past thinking about it. You have:
- ✅ Cursor installed and open on your computer
- ✅ A GitHub account (logged in)
- ✅ A Vercel account (connected to GitHub)
Time so far: ~15 minutes
👩💼 Maya check-in: "Wait, that's it? I have accounts set up and I haven't broken anything yet. Okay. Maybe this is actually doable."
Chapter 2: Your First Project (The Fun Part) ⏱️ ~20 min
What we're building
A simple personal landing page. One page. Your name, a short bio, and a link or two. Something you could share with anyone.
This might sound small, but here's the thing: once you deploy one website, you can deploy a thousand. The first one is the hard part. You're about to crush it.
Step 2.1: Create a New Project in Cursor
- Open Cursor (the app you installed)
- Look for "Open Folder" or go to File → Open Folder
- Create a new folder somewhere you'll remember
- On Mac: Try your Desktop or Documents folder
- On Windows: Same—Desktop or Documents works great
- Name it something like `my-first-website`
- Select that folder and click "Open"
You should now see the folder name in Cursor's sidebar (the left panel). It's empty right now. That's about to change.
Step 2.2: Meet Your AI Assistant
Here's where the magic happens. Cursor has a built-in AI that you can talk to. It understands what you want to build and writes the code for you.
How to open the AI chat:
- Press Cmd+L (Mac) or Ctrl+L (Windows) for the chat panel
- Or look for a chat/assistant icon in the interface
You should see a text box where you can type. This is where you talk to the AI.
How to talk to Cursor like a PM, not a beginner
The secret to getting great results from Cursor? Talk to it like you're a product manager giving instructions to a developer. Be clear. Be specific. Give constraints.
🎯 The three-part prompt formula: Describe → Constrain → Iterate
"Create a landing page with my name as the headline and a short bio."
"Use a dark gradient background. Keep everything in one HTML file. Make it mobile-friendly."
"Make the heading bigger. Change the gradient to purple-blue. Add more spacing."
Bad prompt vs. Better prompt
❌ Vague prompt
"Make me a website"
Result: Generic, guesses everything, probably not what you wanted.
✅ Specific prompt
"Create a personal landing page with a centered layout, dark gradient background (purple to black), my name as a large headline, 2 sentences of bio text, and links to GitHub and LinkedIn. Use clean, modern styling. Keep it all in one HTML file."
Result: Exactly what you described, styled how you wanted.
When Cursor is confusing, say this
Keep these phrases handy. They work every time:
- 📝 "Explain what you just did in plain English." — Gets you a human-readable summary.
- 🔍 "Show me only the parts you changed." — Cuts through the noise.
- 🎓 "Simplify this code and keep it beginner-friendly." — Removes unnecessary complexity.
- ❓ "Why did you do it this way instead of [other way]?" — Learn the reasoning.
- 🔄 "That's not quite right. Try again with [specific feedback]." — Iterate without frustration.
Step 2.3: Your First Prompt (Copy-Paste This)
Here's exactly what to type (or copy-paste) into the AI chat:
I'm building my first website ever. Please create a simple landing page for me with:
1. A centered layout
2. My name as the title (use "Alex" as a placeholder)
3. A short bio paragraph (2-3 sentences, placeholder text is fine)
4. Links to GitHub and LinkedIn (use # as placeholder URLs)
5. A dark gradient background (something modern, maybe purple to black)
6. Clean, professional styling with good typography
Create this as a simple index.html file with inline CSS so everything is in one file. Make it look beautiful and work well on mobile.Press Enter (or click Send).
🎭 What just happened?
You asked an AI to write code for you. In plain English. It's going to create a complete webpage—HTML, CSS, everything—based on your description. This is not a drill. Welcome to the future.
Step 2.4: Accept the Changes
After a moment, Cursor will show you what the AI created. You'll see code appear (probably with green highlighting for new lines).
Here's what to do:
- Look at the code preview. It should be a file called `index.html`
- If it looks reasonable (lots of HTML tags, some style stuff), accept it
- Click "Accept" or press Tab or Enter (depending on how Cursor prompts you)
The file should now appear in your sidebar. Click on it to see the full code.
🔧 Troubleshooting
If you don't see the file: Check the sidebar on the left. If there's no sidebar, press Cmd+B (Mac) or Ctrl+B (Windows) to toggle it.
If the AI says something went wrong: Just type "try again" and it will.
Step 2.5: Preview Your Website (Locally)
Let's see what you built!
The easy way:
- Find the `index.html` file in your folder (either in Cursor's sidebar or in your regular file explorer)
- Right-click it
- Choose "Open with..." and select your browser (Chrome, Safari, Firefox, Edge)
Your website should appear! It's running on your computer only right now—nobody else can see it. But you will.
🎉
Pause and actually celebrate
You just built a website. It exists. You can see it in your browser. Most people never get this far. You're already ahead of 90% of folks who "want to learn to code."
Step 2.6: Customize It (Make It Yours)
Time to replace the placeholders with your real info. Go back to Cursor and talk to the AI:
Please update the index.html file with my real information:
Name: [YOUR ACTUAL NAME]
Bio: [WRITE 2-3 SENTENCES ABOUT YOURSELF]
GitHub: [YOUR GITHUB URL] (or remove this link if you don't have one)
LinkedIn: [YOUR LINKEDIN URL] (or remove this link if you don't have one)
Keep the same design, just update the text content.Accept the changes. Refresh your browser. See your real info appear.
Chapter 2 Checkpoint
🌟 Look at what you've built
You talked to an AI, it wrote code, and now you have a beautiful webpage. You should have:
- ✅ A folder called something like `my-first-website`
- ✅ An `index.html` file inside it
- ✅ A beautiful landing page when you open it in your browser
- ✅ Your actual name and info on the page
Time so far: ~30 minutes
👩💼 Maya check-in: "I just built a webpage. By talking to it. In English. My name is on a webpage that I made. I need to text someone about this."
Chapter 3: Putting It on the Internet ⏱️ ~10 min
This is the part that used to require server configuration, FTP clients, SSH keys, and a lot of crying. With Vercel, it's approximately five clicks.
What "deploy" means — three ways
Step 3.1: Create a GitHub Repository
A "repository" (or "repo") is just a folder in GitHub's cloud. We need to put your website files there.
Here's what to do:
- Go to github.com and log in
- Click the green "New" button (or go to github.com/new)
- Fill in:
- Repository name: `my-first-website` (or whatever you like)
- Description: "My first website built with Cursor and Vercel" (optional)
- Public is fine (your code will be visible, which is normal)
- Don't check any boxes about README or gitignore for now
- Click "Create repository"
You'll see a page with instructions. Don't panic. We're about to do this the easy way.
🔧 Troubleshooting
If you don't see the green "New" button: Look in the left sidebar, or click the "+" icon in the top right corner and select "New repository."
Step 3.2: Upload Your Files to GitHub
Since we're keeping this super simple (no terminal required!), we'll use GitHub's upload feature.
Here's what to do:
- On your new repo page, look for "uploading an existing file" link and click it
- Drag your `index.html` file from your computer into the upload area
- Scroll down
- Add a commit message like "Add my first website"
- Click "Commit changes"
Your file is now in GitHub! Refresh the page and you should see index.html listed.
🎓 What's a "commit"?
A commit is like a save point in a video game. It captures a snapshot of your files at that moment. If you mess something up later, you can go back to any previous commit. Think of it as infinite undo with notes attached.
Step 3.3: Deploy with Vercel (The Magic Moment)
✨ This is the moment everything changed for me
The first time I saw a URL that I made show up on my phone, something clicked. It wasn't "playing pretend developer" anymore. It was real. A thing I built, accessible from anywhere in the world. You're about to feel that.
Here we go. The moment where your website goes live on the actual internet.
Here's what to do:
- Go to vercel.com and log in
- Click "Add New..." → "Project"
- You should see your GitHub repositories listed
- Find `my-first-website` and click "Import"
- Leave all the settings as default (Vercel is smart and figures it out)
- Click "Deploy"
🔮 What Vercel is doing behind the scenes for you
While you wait 30-60 seconds, Vercel is: creating a project, downloading your code from GitHub, building your website, copying it to fast servers on every continent, setting up HTTPS security, and creating a unique URL just for you. All automatically. For free.
Step 3.4: Visit Your Live Website
When the deploy finishes, you'll see a success screen.
👀 What you'll see on the success screen
Look for: a green checkmark ✓, a little rocket or celebration icon 🚀, and a URL that looks something like:
https://my-first-website-yourusername.vercel.app
Click the preview image or the URL. Your website is live!
🔧 Troubleshooting
If you don't see your repo listed: Make sure you authorized Vercel to access GitHub. Go to Settings → Git and reconnect if needed.
If the deploy fails: Click on the deployment to see the error. Usually it's a typo in the HTML. Ask Cursor to "fix this error: [paste error message]"
📱 The Phone Test Ritual
This is important. Do this now:
- Open your new URL on your phone (text it to yourself or type it in)
- Take a screenshot
- Save it somewhere
That screenshot is your first shippable artifact. Your proof. The thing you can show anyone who asks "so what have you actually built?"
This isn't just a website. It's evidence that you can do hard things.
Chapter 3 Checkpoint
🚀
You Did It
That URL works on any device, anywhere in the world. Text it to a friend. Put it on your resume. Tweet it. You built this. It's real. It's live. You're a website creator now.
- ✅ A GitHub repository with your `index.html` file
- ✅ A Vercel project connected to that repo
- ✅ A live URL that shows your website
- ✅ A screenshot on your phone (you did it, right?)
Time so far: ~45 minutes
👩💼 Maya check-in: "I texted the link to my partner. They opened it on their phone in another room. My website. On their phone. I might cry. Is that weird? I don't care. I made something."
Chapter 4: Making Changes (The Real Superpower) ⏱️ ~10 min
Here's where it gets fun. Every time you make a change and push it to GitHub, Vercel automatically deploys the new version. No extra steps.
Step 4.1: Make a Change in Cursor
Let's add something new to your site. Open Cursor and talk to the AI:
Please add a "Projects" section below the bio with 3 placeholder project cards. Each card should have:
- A project title
- A short description (1-2 sentences)
- A colored border or accent that matches the overall design
Keep the same design aesthetic and make it look polished.Accept the changes.
Step 4.2: Preview Locally First (The "Don't Break Prod" Habit)
Before pushing anything live, always preview locally. This is especially important once real people are visiting your site.
For simple HTML files:
Just open index.html in your browser and refresh after changes.
For projects with a dev server (React, Next.js, etc.):
npm run devThis starts a local server (usually at http://localhost:3000). Every time you save a file, it updates automatically. You can click around, test everything, and break stuff freely—nobody sees it but you.
🛑 The "Real Users Are Watching" Rule
Once your site has actual visitors, slow down the deploy loop. Preview everything locally first. Test on your phone using your local network. Only push when you're confident. Nothing says "amateur hour" like your homepage breaking while someone's reading it.
Ask me how I know this. 😅
Quick dev server commands to know:
| Command | What it does |
| --------- | -------------- |
| `npm run dev` | Starts local preview server |
| `npm run build` | Creates production-ready files |
| `npm run lint` | Checks for common mistakes |
| `Ctrl+C` / `Cmd+C` | Stops the dev server |
If something's off, tell Cursor what to fix before you push.
Step 4.3: Push the Update to GitHub
Now let's get this live!
The visual way (no terminal):
- Go to your repository on GitHub
- Click on the `index.html` file
- Click the pencil icon (Edit this file)
- Select all and delete the old content
- Go back to Cursor, copy the entire new `index.html` content (Cmd+A then Cmd+C, or Ctrl+A then Ctrl+C)
- Paste it into GitHub's editor
- Scroll down, add a commit message like "Add projects section"
- Click "Commit changes"
Wait 30-60 seconds, then refresh your live Vercel URL.
Your changes are live!
⚡ This is the workflow
Edit in Cursor → Preview locally → Push to GitHub → Vercel deploys automatically. That's it. That's the whole thing. Professional developers do exactly this, just with more files.
🔧 Troubleshooting
If changes don't appear: Hard refresh your browser (Cmd+Shift+R or Ctrl+Shift+R). Browsers cache aggressively.
If Vercel shows an error: Check your Vercel dashboard for the error message, then ask Cursor to fix it.
Chapter 4 Checkpoint
🔄 You've completed your first loop
You now know how to: build something → see it locally → push it live → update it. This is the core of web development. Everything else is just variations on this theme.
Later in this article, I'll show you The JG Loop—the complete 9-step system I use for every project. It builds on what you just learned.
Chapter 5: Level Up - Using Git Properly (Optional) ⏱️ ~10 min
🎓 Terminal Curiosity Corner
This section is optional. Everything above works without it. But if you want to peek behind the curtain and use the "real" developer workflow, this is how. You'll feel like a hacker. It's fun.
Ready for a slight upgrade? Let's set up Git in Cursor so you don't have to copy-paste to GitHub every time.
Step 5.1: Set Up Git in Cursor
First, make sure Git is installed on your computer:
Windows:
- Download Git from git-scm.com
- Run the installer with default settings
Mac:
- Open Terminal (search for it in Spotlight)
- Type `git --version` and press Enter
- If it's not installed, your Mac will prompt you to install it
Step 5.2: Connect to GitHub in Cursor
- In Cursor, open the command palette (Cmd+Shift+P on Mac, Ctrl+Shift+P on Windows)
- Type "Git: Clone" and select it
- Paste your repository URL (find it on GitHub by clicking the green "Code" button)
- Choose where to save it
- Open the cloned folder in Cursor
Step 5.3: The Faster Workflow
Now when you make changes:
- Edit files in Cursor
- Look for the "Source Control" icon in the sidebar (branch-like symbol)
- See your changes listed
- Type a message describing what you changed
- Click "Commit" then "Sync" (or "Push")
Done! Changes go to GitHub, Vercel deploys automatically.
🔧 Troubleshooting
If Git asks for credentials: It might open a browser window for GitHub login. Complete that and it should remember you.
If "Push" fails: Make sure you cloned your own repo, not someone else's fork.
Vercel Extras: Your Next Buttons
Now that you've deployed, here are two quick upgrades you might want:
Custom Domain (yourname.com)
Want your site at a real domain instead of .vercel.app?
- Buy a domain from Namecheap, Google Domains, or similar (~$10-15/year)
- In Vercel, go to your project → Settings → Domains
- Click "Add" and type your domain (like `yourname.com`)
- Vercel gives you DNS records to add at your domain registrar
- Once connected, Vercel gives you HTTPS automatically (the little lock icon)
That's it. No SSL certificates to manage. No server configuration. Just type and click.
See Who's Visiting (Analytics)
Curious who's looking at your site? Vercel has built-in analytics.
Go to your project → Analytics tab. You'll see visitors, page views, and where traffic comes from. It's simple but useful—especially if you're building something you want to share.
Don't Worry About Money (Yet)
💚 The Hobby plan is enough
For personal projects, portfolios, learning, and even small business sites, the free Hobby plan works great. You only need to think about paid plans when you're getting serious traffic (millions of visitors) or building something commercial. That's a good problem to have—and you'll figure it out when you get there.
Why Vercel Is Perfect for Beginners
Let me translate Vercel's features into human benefits:
| Technical Feature | What It Actually Means for You |
| ------------------- | -------------------------------- |
| "Automatic deployments" | Change code → website updates automatically. No extra steps. |
| "Preview deployments" | Every change gets its own test URL before going live. Safe to experiment. |
| "Global CDN" | Your site loads fast everywhere—Tokyo, Toronto, Tanzania. |
| "Free Hobby tier" | Build and host projects without paying a cent. Seriously. |
| "No server management" | You never touch servers. They handle all of that. Forever. |
| "Rollback" | Pushed something broken? One click to restore the previous version. |
| "Automatic HTTPS" | Security is handled. You get the little lock icon for free. |
🛡️ You can't really mess this up
Every deploy is saved. Every version is recoverable. Preview URLs let you test before going live. If something goes wrong, click rollback. Vercel has your back.
Why Cursor Is Magic for Non-Developers
Cursor isn't just a code editor—it's a code editor with a genius friend built in.
| What You'd Normally Need | What Cursor Gives You |
| -------------------------- | ---------------------- |
| Years of learning syntax | Ask in plain English, get working code |
| Stack Overflow searching | AI explains errors and fixes them |
| Documentation diving | Just describe what you want |
| Debugging skills | "Why isn't this working?" → AI tells you |
You're not "fake coding" when you use AI. You're directing, editing, and making decisions. The AI is a tool. You're the architect.
The JG Loop: How I Actually Build
You've learned the basics. Now let me show you the system I use for everything—every page, every feature, every project. I call it The JG Loop.
🔄
Think it → Build it → Ship it → Polish it → Stress-test it → Ask AI to roast it → Repeat
This loop is how quality quietly compounds over time. Each cycle gets faster, sharper, and more intuitive.
The JG Loop — Quick Reference
Think small, ship fast, let the tools coach you, then do it again sharper.
Now let's break each step down in detail...
Step 1: Spark the Idea 💡
Start with a tiny, concrete outcome: a section, a page, or a micro-feature. Not a whole product. Write a one-paragraph spec in plain English so both you and the AI know the target.
Example: "I want an About page with my photo, a two-paragraph bio, and three fun facts about me. Clean design that matches my homepage."
Step 2: Make the First Version ⚡
Use Cursor to generate the first pass. You're aiming for "works end-to-end," not "perfect." Let AI scaffold, but you decide structure, naming, and what "done for now" looks like.
Mindset: First drafts are supposed to be rough. Get something on screen. You'll fix it in the next steps.
Step 3: Push It Live Fast 🚀
Wire it up to Git and push. Every meaningful change gets a commit, then a deploy. You always have a real URL and a rollback point. This keeps you shipping instead of tinkering forever.
Rule: If you can't show it to someone, it doesn't exist yet. Ship early, ship often.
⚠️ Once you have real visitors: Slow down. Run npm run dev and preview locally before every push. "Ship fast" becomes "ship confidently" when people are actually watching your site.
Step 4: Fix the Experience on Every Screen 📱
Once it's live, switch into "designer QA" mode:
- Tighten the layout for both mobile and desktop (spacing, font sizes, tap targets)
- Use responsive techniques so it feels native on a phone, not just "shrunk desktop"
- Test on your actual phone, not just the browser's device emulator
Pro tip: If something feels slightly off on mobile, it's very off. Trust your thumbs.
Step 5: Run Lighthouse Like a Coach 📊
Open Chrome DevTools → Lighthouse → Generate Report. Treat the scores like coaching notes, not grades. Focus on the big levers:
| Metric | What It Measures |
| -------- | ------------------ |
| LCP (Largest Contentful Paint) | How fast the main content appears |
| FCP (First Contentful Paint) | How fast anything appears |
| TTI (Time to Interactive) | How fast users can click things |
| Accessibility | Can everyone use your site? |
| SEO | Will search engines find you? |
Goal: You don't need 100 everywhere. Aim for green scores on mobile. That's the hard one.
Step 6: TypeScript Pass — Make the Code Honest 🔍
If you're using TypeScript (you should eventually), turn on strict mode and fix what breaks. Types surface hidden assumptions and edge cases you were mentally hand-waving away.
For beginners: Skip this step for now. Come back to it when you're ready to level up. The rest of the loop works without it.
Step 7: Ask AI to Critique and Optimize 🤖
Now that it works, invite AI back in as a reviewer, not a builder. Try these prompts:
- 🔍 "Scan this codebase for simplifications, performance wins, and bugs-in-waiting."
- 🧹 "Show me anything you'd refactor for clarity or maintainability."
- ⚡ "What would make this page load faster?"
- ♿ "Check this for accessibility issues."
Let AI propose changes, then accept or reject like a senior dev doing code review. You're the decision-maker.
Step 8: Test It Like a Real User 👆
Hit the live URL from:
- Your phone (different network, thumbs, real scrolling)
- Your laptop/desktop (keyboard, big screen, different browser)
- Someone else's device if you can borrow one
Look for "feels wrong" moments: jank, layout jumps, slow loads, awkward flows. If it annoys you, it annoys everyone.
Step 9: Loop Again, But Smaller and Sharper 🎯
You never "finish"—you tighten the loop. Next cycle:
- The idea is smaller
- The spec is clearer
- The AI prompts are sharper
- The Lighthouse + TypeScript passes get faster
That's how quality quietly compounds over time.
🔄 The JG Loop summarized
Think → Build → Ship → Polish → Measure → Review → Repeat. Each cycle, you get faster. Each project, you get better. That's the whole game.
What You Could Build Next
Now that you know the workflow, here are ideas:
| Project | Difficulty | What You'd Learn |
| --------- | ------------ | ------------------ |
| Personal blog | ⭐⭐ | Multiple pages, navigation |
| Link-in-bio page | ⭐ | Styling, custom domains |
| Project portfolio | ⭐⭐ | Dynamic content, images |
| Landing page for an idea | ⭐⭐ | Forms, email capture |
| Recipe collection | ⭐⭐ | Lists, organization |
| Resume website | ⭐⭐ | Professional design, PDF links |
All of these follow the exact same workflow you just learned.
Frequently Asked Questions
Q: Is Vercel really free?
For personal projects and learning? Yes, completely free. The Hobby plan includes everything you need. Paid tiers exist for businesses and high-traffic sites, but you won't need those for a long time. I've run dozens of sites on the free tier.
Q: Is Cursor free?
Cursor has a free tier with limited AI requests. For serious building, Pro is $20/month. But the free tier is enough to complete everything in this article—and probably your next few projects too.
Q: What if I want to add more pages?
Just ask Cursor! "Add an About page linked from the homepage" → it creates the files and links them. Same deployment process—push to GitHub, Vercel handles the rest.
Q: I don't understand the code. Is that okay?
Totally fine at first! You'll start recognizing patterns over time. You don't need to understand every line to build cool things. That said, if you're curious, ask Cursor: "Explain what this code does line by line."
Q: What if I break something?
Vercel keeps every version of your site. Click Deployments in your dashboard, find a working version, and click "Promote to Production." You're restored in seconds. You literally cannot permanently break anything.
The Mindset Shift
Before AI tools like Cursor, building websites meant:
- Learning HTML, CSS, JavaScript (months)
- Understanding frameworks (more months)
- Figuring out hosting, domains, SSL (tears)
- Debugging errors with no help (rage)
Now it means:
- Describe what you want
- Let AI write the code
- Click deploy
- Have a website
You are not "cheating" by using AI. You're using the best available tools. Architects don't cut their own wood. They design and direct.
Your Action Items
Here's exactly what to do after reading this:
- Build one more page - Add an "About" or "Contact" page to your site
- Share your URL - Text it to at least one person. The accountability matters.
- Experiment - Ask Cursor to add something fun: an animation, a color change, a hover effect
- Take your phone screenshot - If you haven't already, do the phone test ritual
- Bookmark this - You'll want to reference the steps again
You're now ahead of most people you know
Let that sink in for a moment.
Most people who "want to learn to code" never write a single line. Most people who start a tutorial quit halfway through. Most people who finish a tutorial never ship anything to a real URL.
You have a live website. Built with AI. Deployed on a platform used by Netflix, TikTok, and The Washington Post.
You're not just "learning to code." You're building things. Real things. Things with URLs.
The gap between "I want to build something" and "I built something" is one that most people never cross. You crossed it. Today.
👩💼 Maya's final check-in: "I came into this thinking I was going to embarrass myself. Now I have a website. Like, an actual website. My coworker asked how I did it and I said 'Oh, I just used Cursor and Vercel.' Like it was nothing. Like I do this all the time. Maybe now I do?"
What's Next?
You've built your first website. You've deployed it. You've updated it. You're no longer a "non-technical person"—you're someone who builds things.
The next guide shows you how to add real functionality: contact forms that actually email you, multiple pages with shared navigation, and the project structure that scales.
Ready for more?
Learn how to add contact forms, multiple pages, and real interactivity to your sites.
Continue to Intermediate Guide →Final words
I meant what I said at the beginning. I genuinely believed I wasn't "technical enough" to build websites. I thought it was for other people—people with degrees and experience and some innate talent I didn't have.
That was fear talking. And fear is a liar.
You just proved it wrong.
You have a live website. You built it with AI. You deployed it with Vercel. You're part of the club now.
Go build something else. And when you do, tell me about it.
📚 Related Resources
Navigate the series
← Previous
You're at the beginning
Deep Dive →
Calm Rituals Before Code
Master the setup process with AI-ready documentation