Advanced 20 min

Full Project: Idea to Launch

This is it — the final lesson. You're going to take everything you've learned across this course and build a complete website from nothing but an idea. No templates. No hand-holding. Just you and Claude, working through the full workflow.

By the end, your site will be live on the internet with a real URL you can share with anyone in the world. Let's go.

The Complete Workflow

Before we start building, here's the full pipeline from idea to launch. Every step builds on the one before it. This is the same workflow professional developers use — you just happen to be doing it in plain English.

Step 1

Choose Your Idea

Pick a business, topic, or cause that you want to build a website for.

Step 2

Create the Project

Set up a folder, open Claude Code, and write a CLAUDE.md with your brand rules.

Step 3

Research

Ask Claude what the best sites in your niche include. Learn what visitors expect.

Step 4

Write the Brief

Plan every page — what goes where, what the structure looks like, what's must-have.

Step 5

Find Images

Download free, high-quality stock photos that match your brand and content.

Step 6

Build

Construct each page one at a time, reviewing as you go.

Step 7

Quality Check

Review everything — mobile, links, images, consistency. Fix what needs fixing.

Step 8

Deploy

Push it live to the internet with a single command. Share your URL.

Eight steps. That's the whole thing. Let's walk through each one with a real example — a bakery website called Golden Crust Bakery.

Step 1 — Choose Your Idea

The idea doesn't need to be groundbreaking. Pick something you can picture clearly — a real or fictional business, a personal portfolio, a community project. If you can describe it in one sentence, it's ready to build.

Simple

  • Personal portfolio
  • Recipe blog
  • Hobby showcase

Medium

  • Restaurant or bakery
  • Gym or fitness studio
  • Event or conference

Challenge

  • Non-profit organization
  • Online course
  • Community directory

For this walkthrough, we're building a site for Golden Crust Bakery — a family-owned bakery in Austin, Texas. You can follow along with this example or swap in your own idea at every step.

Step 2 — Set Up Your Project

Create a folder, open Claude Code in it, and immediately set up your CLAUDE.md. This is the foundation that keeps everything consistent from the very first file.

Creating the project
~ $ mkdir golden-crust-bakery
~ $ cd golden-crust-bakery
golden-crust-bakery $ claude

Now tell Claude about the project. Be specific about the look and feel you want:

Setting up CLAUDE.md
you: Create a CLAUDE.md for a bakery website called "Golden Crust Bakery". It's a family-owned bakery in Austin, Texas. Use warm colors — cream, golden yellow, chocolate brown. Playfair Display for headings, Lato for body. Photography-heavy, welcoming feel.
Claude: I've created CLAUDE.md with your brand rules:
- Colors: Cream (#FFF8F0), Gold (#D4A843), Brown (#4A3222)
- Fonts: Playfair Display headings, Lato body
- Warm, inviting photography style
- Mobile-first, accessible
Created CLAUDE.md

That's it. Every page Claude builds from this point forward will follow those rules. You'll never need to repeat your color palette again.

Step 3 — Research

Before you plan anything, ask Claude what makes a great website in your niche. You'll discover pages and features you wouldn't have thought of on your own.

Researching bakery websites
you: Research what makes a great bakery website. What pages do successful bakeries include? What information do customers need most?
Claude: Based on top-performing bakery websites, here's what customers look for:
Must-have pages:
- Home — Hero image, featured products, hours & location
- Menu — Full product list with prices and photos
- About — The bakery's story, the family, sourcing
- Gallery — Beautiful shots of products and the shop
- Contact — Address, hours, phone, map, order form
Key information customers look for first:
1. Hours of operation
2. Location and directions
3. Menu with prices
4. Online ordering or phone number
5. Customer reviews

Now you know exactly what pages to build and what content matters most. The research phase takes two minutes but saves hours of rework later.

Step 4 — Write the Brief

A brief is your blueprint. It maps out every page before you write a line of code. Think of it as the plan that prevents rebuilds — you wouldn't build a house without a floor plan, and you shouldn't build a website without a brief.

brief.md
1# Golden Crust Bakery — Project Brief
2
3## Pages
4
5### 1. Home (index.html)
6- Hero: Full-width image of fresh bread, headline
7 "Baked Fresh Every Morning"
8- Featured products grid (4 items with photos)
9- Testimonial section (3 customer reviews)
10- Hours and location bar in footer area
11
12### 2. Menu (menu.html)
13- Categories: Breads, Pastries, Cakes, Drinks
14- Each item: name, price, short description, photo
15- Filter buttons for categories
16
17### 3. About (about.html)
18- The family's story (how the bakery started)
19- Photo of the team
20- Sourcing and ingredients philosophy
21
22### 4. Gallery (gallery.html)
23- Masonry grid of bakery photos
24- Lightbox on click
25
26### 5. Contact (contact.html)
27- Address, phone, email
28- Embedded Google Map
29- Contact form (name, email, message)
30- Full hours of operation
31
32## Design Rules
33- Every page must have at least 2 images
34- Consistent nav on all pages
35- Footer with hours and address on every page

When you have this brief, you're not guessing anymore. You know exactly what you're building, page by page, section by section.

Step 5 — Find Images

A website without images is a wall of text. Before building a single page, stock up on photos that match your brand. Free sources like Pexels, Unsplash, and Pixabay have thousands of professional-quality images.

Finding stock photos
you: Find free stock photos for the bakery site: a hero image of fresh bread, close-ups of pastries, a cozy bakery interior, and the team working. Download them to images/
Claude: Found and downloaded 8 images:
Downloaded images/hero-bread.jpg (1920x1080)
Downloaded images/pastries-closeup.jpg (1200x800)
Downloaded images/bakery-interior.jpg (1600x1067)
Downloaded images/team-working.jpg (1400x933)
Downloaded images/croissants.jpg (1200x800)
Downloaded images/cake-display.jpg (1200x800)
Downloaded images/coffee-pastry.jpg (1200x800)
Downloaded images/sourdough.jpg (1200x800)

Now every page in your brief has real photos waiting for it. No placeholders, no "we'll add images later." The visuals are ready before you build.

Step 6 — Build

Here's the key: build one page at a time. Open each page in your browser, review it, and iterate before moving to the next. Don't try to build all five pages in one go.

Building the home page
you: Build the home page according to the brief. Hero with "Baked Fresh Every Morning" headline using hero-bread.jpg, featured products grid, testimonial section, hours and location.
Claude: I've built index.html with:
- Full-width hero with text overlay on hero-bread.jpg
- 4-card featured products grid with photos
- 3 customer testimonials with star ratings
- Hours/location bar before the footer
- Consistent navigation for all 5 pages
Created index.html

Open it in your browser. Look at it. Does the hero feel welcoming? Is the text readable over the image? Are the products arranged well on mobile? Once you're happy, move on.

Building the next page
you: Now build the menu page. Categories: Breads, Pastries, Cakes, Drinks. Each item gets a name, price, short description. Use the pastry and bread photos from images/.
Claude: I've built menu.html with 16 items across 4 categories,
filter buttons, and product photos.
Created menu.html

Repeat this for About, Gallery, and Contact. One page at a time, reviewing each before you ask for the next. By the end of this step, you have a complete five-page website.

Step 7 — Quality Check

Before you show anyone your site, run through this checklist. Every professional web developer does this — you should too.

You can also hand this whole process to Claude:

Automated QA
you: Review the entire site for issues. Check mobile responsiveness, image quality, text contrast, and broken links. Fix anything you find.
Claude: Found and fixed 3 issues:
1. Gallery page: lightbox wasn't closing on mobile — fixed
2. Menu page: filter buttons overlapped on small screens — added flex-wrap
3. Contact form: submit button had no hover state — added transition

QA is the difference between "I made a website" and "I made a website I'm proud of." Don't skip it.

Step 8 — Deploy

This is the moment. You're about to put your website on the internet where anyone can see it. And it's surprisingly simple.

Option A: Vercel (Recommended)

Vercel gives you free hosting with a real URL. Install it once, then deploy with a single command.

Deploying to Vercel
golden-crust-bakery $ npm install -g vercel
golden-crust-bakery $ vercel
Vercel CLI 39.0.0
? Set up and deploy? Yes
? Which scope? your-username
? Link to existing project? No
? What's your project's name? golden-crust-bakery
Ready! Deployed to:
https://golden-crust-bakery.vercel.app

That's it. Your website is on the internet. Copy that URL and send it to anyone — they'll see your bakery site, fully functional, loading fast on a global CDN. For free.

Option B: Netlify Drop

If you want something even simpler, Netlify Drop lets you drag your project folder onto a webpage. No command line, no account required. You'll get a live URL in seconds.

Made changes? Just run vercel again (or re-drop on Netlify) to update your live site. Deployment is not a one-time thing — it's part of your iteration cycle.

What You've Accomplished

Take a moment and think about where you started versus where you are now.

Lesson 1
Your first HTML page
Lesson 10
A live 5-page website
Single file
Multi-page site with navigation
"Make it look nice"
CLAUDE.md with brand rules
Copy-paste guessing
Research, plan, build, deploy
localhost only
Live on the internet

You didn't just learn to use a tool. You learned a workflow — a way of thinking about projects that applies to every website, app, or piece of content you'll ever build.

Pro Tip

Your first deployed site won't be perfect, and that's fine. You can always iterate — make changes locally, then run vercel again to update. The best way to learn is to ship something and improve it. Perfection is the enemy of progress.

Where to Go from Here

Finishing this course isn't the end — it's the starting point. Here are some directions you can take your skills next.

Final Course Quiz

Five questions covering everything you've learned across all 10 lessons. Let's see what stuck.

1. What's the first thing you should do when starting a new project?

2. What's the purpose of a project brief?

3. Why use icon libraries instead of emojis?

4. What does "iterate" mean in vibe coding?

5. What command deploys your site to Vercel?

Key Takeaways

Course Complete

You've finished Vibe Coding with Claude Code. You have the skills and the workflow to build anything. Now go ship something.

Lesson 9: APIs & Data Course Home