0 of 0

Build Your Damn Website Summer Camp

THE BUILD CHECKLIST

from blank screen to live link, checking boxes as you go

You're about to turn your message into a live site! You do NOT need to know how to code. You do need to know what you want to say about yourself, which is why we did the Trail Guide first. I definitely recommend finishing that before we get started here. Follow the instructions below, and by the end, you'll have a live website at your own web address that anyone in the world can visit, and you'll know how to change it whenever you want.

How this page works: check the box on each step as you finish it. Your progress saves itself in this browser, on this computer; close the page and come back anytime. Steps only relevant to Mac or Windows hide themselves once you pick yours below. Green-bordered checkpoint boxes tell you what your screen should look like before you move on. If yours doesn't match, stop and fix it before continuing.

What kind of computer are you on?

The question everyone asks

"Do I need a terminal?" No. A terminal is the black screen with green text that hackers use in movies. It exists, developers use it, and you do not need it. We're using the Claude Code desktop app: a normal application with buttons and windows, like Zoom or Spotify. You will never type a command. You will type sentences in English.

PART 1 — Before you build

Think of these as the prerequisites for vibe coding. Budget 30–45 minutes.

1.1 — Get a paid Claude account

Claude Code is not on the free Claude plan. You need Claude Pro. It's the one thing that costs money, but you can just get one month and unsubscribe if you like.

  1. Go to claude.com/pricing
  2. Choose Pro: $20/month, or $200 up front for a year. Pick monthly if unsure; you can cancel anytime.
  3. Create your account, or sign in to your free account and upgrade it.
  4. Write down the exact email address you signed up with. Mixing up two emails is the #1 way this goes wrong.
There's a bigger plan called Max at $100/month. You do not need it. Pro is plenty for this one project.

1.2 — Check your computer can run it

You need
MacmacOS 13 (Ventura) or newer
WindowsWindows 10 or newer
Both4 GB+ RAM, internet connection

MacApple menu (top-left) → About This Mac. Check the version number and Memory.

WinStart menu → Settings → System → About. Check "Edition" and "Installed RAM."

Almost any computer bought in the last 6–8 years is fine.

1.3 — Turn on file extensions

Your computer is hiding part of every filename: it shows index when the file is index.html. We need to see the whole thing.

Mac
  1. Open Finder.
  2. Menu bar: Finder → Settings (older Macs: Preferences).
  3. Click the Advanced tab.
  4. Tick Show all filename extensions. Close the window.
Win
  1. Open File Explorer (the folder icon in your taskbar).
  2. Click View in the toolbar.
  3. Hover Show, tick File name extensions. (Windows 10: View tab → tick the File name extensions checkbox.)

✅ Checkpoint

Open any folder with photos. Files now read beach.jpg or IMG_4471.HEIC, not just beach. If you can see the bit after the dot, you're done.

1.4 — Windows only: install Git first

Do not skip

Claude Code cannot touch your files without this. It's a background tool; you'll never open it. It just needs to exist.

  1. Go to git-scm.com/downloads/win
  2. Download 64-bit Git for Windows Setup.
  3. Open the downloaded file. If Windows asks "allow this app to make changes?", click Yes.
  4. The installer asks a LOT of questions over ~10 screens. Click "Next" on every one without changing anything. The defaults are correct. Then Install, then Finish.

Done. You will never think about this again.

1.5 — Install the Claude Code desktop app

Mac
  1. Download: Claude for Mac (a file like Claude.dmg).
  2. Open it. A window shows the Claude icon and an Applications folder.
  3. Drag the Claude icon onto the Applications folder.
  4. Open Applications, double-click Claude.
  5. If macOS warns "downloaded from the Internet, are you sure?", click Open.
Win
  1. Download from claude.com/download and run the installer.
  2. If SmartScreen says "Windows protected your PC," click More info → Run anyway. (This appears for plenty of legitimate software.)
  3. Find Claude in your Start menu and open it.
On an ARM processor (Surface Pro X and some newer laptops)? Most people are not. If the normal installer refuses to run, use the ARM64 installer.

1.6 — Sign in and confirm the Code tab works

Do not skip. This 20-second check is how you find problems now, instead of when you're mid-build and trying to concentrate.

  1. Open the Claude app and sign in with the account from Step 1.1.
  2. Across the top: Chat, Cowork, Code. Click "Code."

MacOn some machines a box pops up: "The 'git' command requires the command line developer tools." Click Install, agree, wait a few minutes. One-time, normal.

✅ Checkpoint

You're looking at a screen offering a choice of environment, or asking you to pick a folder.

Asks you to upgrade? Your paid plan is on a different account. Sign out, sign back in with the email from Step 1.1. This is the #1 problem people hit.

"403" error? Quit the app completely and reopen.

Once the Code tab opens without complaining, setup is done.

1.7 — Finish your Trail Guide + check your photos

The thinking work — what your site says, who it's for, your story, your proof — lives in The Trail Guide. Finish it before you start building. It ends with a button that hands you a ready-made script for Claude, and that script is what makes the build fast.

Photos still on your phone? Here's how to get them onto the computer:
  • MaciPhone → Mac: AirDrop. Select the photos in your Photos app → share icon → AirDrop → your Mac. They land in Downloads; drag them to your folder.
  • WiniPhone → Windows: email them to yourself (a few at a time), then save the attachments. Or plug the phone in with its charging cable, tap "Allow" on the phone, and copy from the DCIM folder.
  • Android → either: open photos.google.com on the computer, sign in, select, download. Or email them to yourself.
Bonus: photos sent by email or WhatsApp usually arrive already converted to JPG, which sidesteps the iPhone problem below.

⚠️ iPhone photos: check this or your site will break

The Trail Guide doesn't cover this, so do it here. iPhones save photos as HEIC files. Safari displays them. Chrome, Firefox and Edge do not display them at all. If you build on a Mac and check in Safari, your site looks perfect to you while every Windows visitor sees empty boxes where your face should be.

Look at your photo filenames now (you turned extensions on in 1.3). Anything ending .HEIC needs converting to JPG:

Mac
  1. In Finder, select all the HEIC files.
  2. Right-click → Quick Actions → Convert Image.
  3. Format: JPEG. Size: Actual Size. Convert.
  4. Use the .jpeg copies; bin the HEICs.
Win
  1. Double-click the HEIC to open it in Photos. (If Windows offers a free HEIF extension from the Store, accept.)
  2. ⋯ menu → Save as → file type JPG → Save. Repeat per photo.

Stop it at the source for next time: iPhone Settings → Camera → Formats → Most Compatible.

Skipped the Trail Guide? You can still build. At minimum, show up with: a folder of photos (face shot included), a rough bio, the one thing you want visitors to do, your links, and the email you want public. Step 3.1 has a fill-in-the-blanks version of the first prompt for you.

PART 2 — Getting oriented

2.1 — Make a home for your website

Your website is going to be a folder of files on your computer.

Mac
  1. Open Finder → click Documents in the sidebar.
  2. Menu bar: File → New Folder (or Shift+Command+N).
  3. Name it my-website, press Return.
Win
  1. Open File Explorer → click Documents in the sidebar.
  2. Right-click empty space → New → Folder.
  3. Name it my-website, press Enter.
Documents, not Downloads. Downloads folders get cleaned out. Don't let your website live somewhere disposable.

Now move your photos and logo into my-website, from your Gear Check folder or wherever they live. Or skip the middleman: move the Gear Check folder itself into Documents and rename it my-website. Either way, the photos end up loose inside one folder in Documents.

✅ Checkpoint

A folder at Documents → my-website with your photos loose inside it. No sub-folders, no HEIC files.

2.2 — Point Claude at your folder

  1. Open ClaudeCode tab.
  2. Choose environment: Local. (Means "use the files on my own computer." Ignore Cloud, SSH, WSL.)
  3. Click Select folder → navigate to Documents → my-website.

Claude can now read and write files in that folder, and only that folder. It cannot wander into your taxes.

✅ Checkpoint

You see a chat box, with my-website shown as the project name. Wrong folder = everything downstream goes wrong, so check the name.

2.3 — Pick your model

Near the send button is a dropdown of model names. Think of them as engines: Opus 5 is the most capable and thinks hardest; Sonnet 5 is faster and lighter.

For this project: leave the default, or pick Opus 5 for the best judgment on design and writing.

Pro has usage limits. Hit one mid-session? Switch to Sonnet 5 and keep working. It's a strong model; you'll be fine.

2.4 — Understand the permission thing

Before Claude changes anything, it asks. Three modes, switchable anytime:

  • Manual: the default. Claude shows each change, waits for Accept/Reject.
  • Accept edits: Claude just makes changes. Faster.
  • Plan: Claude describes without touching anything.

Start in Manual. Watch two or three changes go by; it demystifies everything fast. Once you're bored of clicking Accept, switch to Accept edits.

Nothing is destroyed either way. Don't like a change? Say "undo that."

PART 3 — Build the thing

3.1 — The first prompt

Two ways in, depending on whether you did the Trail Guide.

🗺️ Did the Trail Guide? Your prompt is already written

  1. Open your Trail Guide in the browser where you filled it in. (Different computer? Click ⬆ Load in its header and pick your saved answers file. Filled it in on your phone? Tap 📋 Copy my build prompt there, paste it into an email or note to yourself, and copy it from that on this computer.)
  2. Scroll to the bottom and click 📋 Copy my build prompt.
  3. Paste it into Claude's chat box.
  4. Before hitting Enter, paste this add-on underneath it (Copy button below). It tells Claude you're new at this.
  5. Hit Enter.
One more thing: I've never coded before, so explain what you're doing as
you go, in plain English. My photos are in this folder. Use them, and tell
me if any are in a format that won't display on the web. Use lowercase
filenames with no spaces for anything you create, and keep index.html at
the top level of this folder.
No Trail Guide? Open this for a fill-in-the-blanks prompt

Copy it, fill in your answers, paste into the box, hit Enter. Don't polish it: messy and honest beats tidy and vague.

I want to build a simple one-page personal website. I've never coded before,
so please explain what you're doing as you go, in plain English.

ABOUT ME
My name is: [your name]
What I do, in one sentence: [one sentence]
More about me: [your 3-5 sentences, pasted raw]

THE ONE THING I want visitors to do: [email me / book a call / follow me / etc.]
My contact email: [email]
My links: [instagram / substack / etc.]

WHAT PEOPLE SAY ABOUT ME (optional):
[paste any quotes, with names]

LOOK AND FEEL
Sites I like the look of: [paste 2-3 URLs]
Colors I love: [colors]
Colors I never want to see: [colors]
Overall vibe in three words: [e.g. warm, bold, uncluttered]

PHOTOS
There are photos in this folder. Please look at what's there and use them.
[Say which one is your main portrait if the filename isn't obvious.]

REQUIREMENTS
- One single page, no separate pages to click through
- Must look good on a phone, since most of my visitors will be on phones
- Build it as plain HTML and CSS, no frameworks, so it's simple for me to
  keep editing later
- The main file must be called index.html and must sit at the top level of
  this folder, not inside a sub-folder
- Use lowercase filenames with no spaces for everything you create

Please build a first version, then tell me what you'd want my feedback on.

Claude starts working: reading your folder, then writing files. Click Accept when it asks. Takes a couple of minutes. Let it finish.

Those last two requirements look fussy and they matter: index.html at the top level is what makes the site work when published, and lowercase filenames prevent a broken-image problem that only appears after you go live.

✅ Checkpoint

Open your my-website folder. A file called index.html sits directly inside it, next to your photos.

3.2 — Look at what you made

  1. Open your my-website folder.
  2. Double-click index.html. It opens in your browser. That's your site.

Opens in a text editor showing a wall of code instead?

MacRight-click index.htmlOpen With → Safari or Chrome.

WinRight-click index.htmlOpen with → Chrome or Edge.

Mac people

Use Chrome for checking your site if you have it. Safari is more forgiving and will show you images most of your visitors can't see. Only have Safari? OK; we catch problems in Step 3.4.

You can also type "show me the site" in Claude; it can open a preview inside the app, next to your conversation, so Claude sees what you see.

The address bar reads something like file:///…/my-website/index.html. Correct: the site is on your computer, not the internet yet. Part 5 fixes that.

✅ Checkpoint

A web page with your name on it, in a browser. Photos visible, not empty boxes or broken-image icons.

3.3 — Now make it yours

The fun part, and where most of your build time goes. Look at your site, find something you don't like, say so in whatever words come naturally:

The header is too big, it's taking up the whole screen on my laptop.
This feels corporate and I want it to feel like a person made it.
Make the background warmer. Less white, more like cream or bone.
I hate the font. Show me three other options and let me pick.
Rewrite my bio to sound less like a résumé and more like how I talk. Keep the facts, lose the stiffness.
Show me what this looks like on a phone.
Add a crinkled paper texture to the background.
Add a photo collage with my running photos.
What would I need to do to add an email address sign-up form?

Tips that make a difference:

  • You can interrupt. Hit stop, or just type your correction and send.
  • "Undo that" works. You cannot break this permanently.
  • Refresh the browser to see changes: MacCmd+RWinCtrl+R after each change. Staring at something that isn't changing? This is why, nine times out of ten.
  • Specific about what's wrong, vague about the solution. "This section feels crowded" beats "add 20 pixels of padding."
  • One change at a time when you're being picky.
  • Ask it to explain. "What did you just change and why?" is a legitimate prompt. This is how you learn.
  • Ask for options. "Give me three versions of that headline."

Keep going until you look at it and think: yeah, that's me.

3.4 — The pre-flight check

Before publishing, paste this in:

Before I publish this, please check and fix:
1. Does it look right on a phone-sized screen?
2. Do all the links work and go where they should?
3. Is my email address correct and clickable?
4. Are any images still in HEIC format? Those won't display in Chrome,
   Firefox or Edge, so tell me which ones and I'll convert them.
5. Do any image filenames have capital letters or spaces? Rename them to
   lowercase with hyphens and update the page, because the web host is
   case-sensitive even though my computer isn't.
6. Are any images so large they'd make the page slow to load?
7. Does the browser tab show a sensible title instead of "Document"?
8. If someone shares this link on social media, what will the preview look
   like? Set that up properly with a title, description and image.
9. Any spelling or grammar mistakes?

Items 4, 5 and 8 are the three that bite people after going live. Number 5 especially: your computer treats Photo.JPG and photo.jpg as the same file. The web host does not. Perfect locally, images gone the moment it's published.

✅ Checkpoint

Claude reported on all nine and fixed what needed fixing. Refresh the browser, one last look.

PART 4 — Set up Cloudflare

Cloudflare Pages will host your site: a computer somewhere keeping it online 24/7. Free. No credit card.

4.1 — Create the account

  1. Go to dash.cloudflare.com/sign-up
  2. Sign up with your email and a password. Use a password manager if you have one.
  3. Verify your email: check your inbox (and spam folder) for the confirmation link.

That's it. Don't buy anything. Don't add a domain. If the dashboard offers you plans or products after signup, ignore all of it; the free tier is what we want, and it's the default. Just have the account.

PART 5 — Go live

This is how we'll make your site publicly viewable with a link.

5.1 — Deploy

You want a PAGE, not a Worker

Cloudflare makes two things that sound similar. Pages is for websites like yours: you hand it a folder of files and it puts them on the internet. Workers is for running code, and it's not what you want. Cloudflare nudges you toward Workers, so read the buttons before you click.

  1. Open the Pages creation screen and sign in. This link skips past the Workers options and goes straight to Pages. (If it lands you somewhere else: click Workers & Pages in the left sidebar → Create application → choose the Pages tab.)
  2. Choose Drag and drop your files, which is the option that does not involve GitHub.
  3. Enter a project name. This becomes your web address: lowercase, numbers, hyphens only. jane-doejane-doe.pages.dev. Your name is usually the answer. Taken? Add a middle initial or your town.
  4. Drag your entire my-website folder in: the folder itself, not the files inside it. (Dragging won't take? There's a browse link, or zip the folder and drag the zip.)
  5. Click Deploy site. Wait ~30 seconds.
Can't find the Pages option, or the dashboard looks different from this? Cloudflare rearranges things. Ask Claude: "I'm trying to deploy a folder of website files to Cloudflare Pages using drag and drop. Walk me through where to click in the current dashboard."

5.2 — Your site is live

Cloudflare shows you a link like https://your-project-name.pages.dev. Click it. That's your website. Live on the Internet, ready for you to send the link to anyone in the world! Send it to hi@angielake.com!

Brand-new sites sometimes show an error for the first minute while Cloudflare wakes them up. Wait 60 seconds, refresh, and it appears.

✅ Checkpoint

Your site loads at the .pages.dev address and your images are showing. Page loads but photos are broken boxes? That's the capital-letters problem; see Troubleshooting.

Open it on your phone before you celebrate. Different device, different browser, no cached files: the honest test.

Now text it to someone. Seriously, before anything else. Text it to a friend and watch them open it.

Two limits you'll never hit: 1,000 files max, 25 MB per file. Your site is maybe 20 files.

PART 6 — Changing your site later

The part that matters most. A site you can't update is a dead end. The loop never changes:

The forever loop: edit → look → drag → live

  1. Open it back up. Claude app → Code tab → my-website in the recent list (or Local → Select folder → Documents → my-website).
  2. Say what you want changed. "Add a section about my October workshop." "Swap my photo for this new one" (drop it in the folder first, and check it's not a HEIC). "The link to my Substack is broken."
  3. Look at it. Double-click index.html, refresh, check before it goes public.
  4. Push it live. dash.cloudflare.com → Workers & Pages → your project → Create a new deploymentproduction → drag the whole folder in again → deploy. Live in seconds, same URL.

Whole folder, every time

Every deployment replaces the whole site with whatever's in your folder. Always drag the entire folder, not just the file you changed.

Safety net: Cloudflare keeps every previous version. Publish something broken → roll back from the dashboard in two clicks.

You can do this from a coffee shop in ten minutes, forever.

Subscriptions and money note: the website itself is free forever. Hosting is free, the .pages.dev address is free, and the site stays up whether or not you pay anyone. The Claude Pro plan ($20/month) is only needed when you want to change things. Some people keep it because they use Claude for everything else too; others cancel and resubscribe for a month when it's time for a big update. Your site does not go down either way.

PART 7 — Your own domain (optional, or save for later)

your-name.pages.dev is a working, shareable address. You could in theory stop here, but it looks more professional to use a custom domain. Want yourname.com, or something else fun? Roughly $10–15/year, the only ongoing cost. I have used GoDaddy easily.

When you're ready

First, which kind do you want?

TypeLooks likePick this if…
Bare domain
most people want this
yourname.com
like angielake.com, Angie's personal site
This site is your main home on the internet. It's the one you put on a business card, say out loud, or print on a sticker.
Subdomainhi.yourname.com
like camp.angielake.com
You already own a domain that's being used for something else, and this site is a separate corner of it. Angie's angielake.com lives on Squarespace, while camp.angielake.com is a Cloudflare page hanging off the same domain: two different sites, one domain.

If you don't already own a domain and this is your main site: get the bare domain. You can always add subdomains to it later.

Bare domain (yourname.com). The domain has to be managed by Cloudflare, so there's one extra step: buy the domain (GoDaddy, Namecheap, Cloudflare itself) → in Cloudflare click Add a site and enter your domain → Cloudflare gives you two nameservers → enter those at the place you bought the domain, replacing what's there → wait for Cloudflare to say the domain is active (a few hours, sometimes up to a day) → then Pages project → Custom domains → Set up a domain.

Subdomain (hi.yourname.com). Simpler, and your domain can stay wherever it's registered. Pages project → Custom domains → Set up a domain → enter the subdomain → add the CNAME record Cloudflare gives you at your registrar, pointing to your-project.pages.dev.

One rule for both

Always add the domain through the Custom domains button in your Pages project. Hand-made DNS records instead = a cryptic 522 error and an hour of confusion.

Pro tip: you can now ask Claude Code exactly how to buy a domain and direct it to your existing site. Tell it which domain you want and where you bought it, and have it walk you through the steps for your setup.

Troubleshooting

The Code tab is asking me to upgrade
Your paid plan is on a different account than the one you're signed into. Check the email in the app matches the one you paid with. #1 issue.
Windows: "Claude can't access my files"
Git isn't installed. Go back to Step 1.4. #2 issue.
Mac: a box wants to install "command line developer tools"
Click Install and wait a few minutes. Normal, one-time.
Images show on my Mac but not on my friend's PC
HEIC files. Safari displays them; Chrome and Edge don't. Convert to JPG (Step 1.7), put the new files in the folder, tell Claude to update the page, redeploy.
Site is live but photos are broken boxes
Almost always capital letters or spaces in filenames: your computer thinks Photo.JPG and photo.jpg are the same file; the web host doesn't. Tell Claude: "The images aren't loading on the live site. Rename every image to lowercase with hyphens and no spaces, and update every reference in the HTML to match exactly." Redeploy. Failing that, check the images are inside the folder you uploaded.
I changed something but the page looks the same
Refresh: Cmd+R (Mac) / Ctrl+R (Windows). Live site: force a full refresh with Cmd+Shift+R / Ctrl+Shift+R.
index.html opens as a wall of code
Right-click it → Open With → pick your browser.
Dragging my folder to Cloudflare fails
Check no file is over 25 MB (usually an oversized photo or a video). Make sure you dragged the folder itself. If dragging misbehaves, zip the folder and drag the zip.
Deployed, but I get a 404
index.html isn't at the top level of what you uploaded; it's probably one folder deeper. Drag my-website itself, not a folder containing it.
I published something and now I hate it
Cloudflare dashboard → your project → Deployments → find the earlier one → roll back.
I closed everything and can't find my work
It's in Documents/my-website. Still there. Open Claude, Code tab, pick that folder again. Your conversation history is in the sidebar too.
Claude did something weird and the site looks wrong
Say "Undo the last change" or "Go back to how it looked before that." Badly tangled? "Something's broken. Look at the page, figure out what's wrong, and fix it."
I hit my usage limit
Switch the model dropdown to Sonnet 5 and keep going. Or wait; Pro limits reset on a rolling basis.
Claude asked me a technical question I don't understand
Say exactly that: "I don't know what that means. Pick whatever's simplest and explain what you chose." This is a fully legitimate answer and Claude handles it well. You never have to pretend to know things.
My Trail Guide answers disappeared
They live in the browser you filled them in with, on that device. Opened a different browser or cleared your history? Click ⬆ Load in the Trail Guide header and pick the answers file you saved in Step 1.7.

Glossary

All the words, translated

Folder: where your website lives. Yours: Documents/my-website.

index.html: the main page. Every website has one. Don't rename it; don't let it slip into a sub-folder.

HTML: the structure and words of the page. CSS: the colors, fonts, spacing.

HEIC: the photo format iPhones use. Doesn't work on most browsers. Convert to JPG.

Deploy / publish: copying your folder onto the internet.

Hosting: the service keeping your site online 24/7. Yours: Cloudflare Pages. Free.

Domain: a web address you own, like yourname.com. ~$12/year. Optional.

DNS: the phone book of the internet, connecting a domain to the site it points to.

Cache: your browser's memory of a page. Why a refresh sometimes shows the old version.

Terminal: the scary black screen. You are not using it. It's fine.

Git: a background tool Windows needs. You'll never open it.

Prompt: what you type to Claude. That's all it means.

Pages vs. Workers: two Cloudflare products. Pages puts a folder of files on the internet, which is what you want. Workers runs code, which you don't need.

THE POINT

Your website is a folder on your computer that you can drag onto the internet whenever you want. That's the whole secret. Not a subscription you're trapped in, not a platform that changes its pricing on you. You own the folder. You control what's in it. You can update it forever, for free.

You did not learn to code. You learned something more useful: you can build and change your own corner of the internet whenever you feel like it.

Go be freakin' awesome about it.

Progress saves in this browser, on this computer.