Build a single-page site, push it to GitHub, and point a domain at it — all from your browser. No terminal required. No IDE required. No previous coding experience required. Prior enthusiasm optional.
You'll need a few accounts set up. If you already have these, skip ahead. If you don't, this takes about five minutes. Ten if you forget your password to something.
Go to claude.ai and sign up (or log in). A Pro plan gets you Claude Code access — it's the agentic coding mode built right into the browser.
Free tier works fine. You'll create a repository on github.com and enable GitHub Pages to host your site.
Buy a domain from any registrar. Sign up for Cloudflare (free plan). You'll point the domain's nameservers at Cloudflare.
Claude Code runs right in your browser at claude.ai. You talk to it in plain English, and it writes code, creates files, and builds your project in a cloud environment. Think of it as an extremely capable intern who never takes lunch breaks, types at 900 WPM, and doesn't need you to install anything.
We're starting on GitHub because Claude Code in the browser can connect directly to a repo and push your code for you. No downloading, no uploading, no file-juggling. Set up the repo first, and Claude handles the rest.
Head to github.com and create a new repository:
good-boy-walks)While you're here, go ahead and turn on GitHub Pages so your site goes live the moment Claude pushes code to it:
Your site will be live at https://yourusername.github.io/good-boy-walks/ as soon as there's an index.html in the repo. Right now it'll just show the README — we'll fix that in Step 2.
Now for the fun part. Head to claude.ai and start a new Claude Code session connected to your GitHub repo. Claude Code can read, write, and push code directly — no manual file transfers needed.
On claude.ai, start a new conversation and select Claude Code mode. Connect it to your GitHub repository — you'll be prompted to link your GitHub account if you haven't already. Select the good-boy-walks repo you just created.
Tell Claude Code what you want. Be specific about the kind of site — the more detail, the better the output.
Claude Code will create the files directly in your connected repo. You'll typically get an index.html file — and possibly a styles.css if the styles warrant their own file.
We ran exactly this prompt through Claude Code and published the output. Check out the finished Good Boy Walks site →
Don't love something? Just say so. Claude Code keeps the full conversation context, so you can refine as you go.
Keep going until you're happy. You can ask Claude Code to change colors, swap layouts, add animations, rewrite copy — whatever you need.
When you're satisfied, tell Claude Code to commit and push. Since it's already connected to your repo, this is a one-liner:
That's it. Your code is on GitHub. Since you already enabled GitHub Pages in Step 1, your site will be live at https://yourusername.github.io/good-boy-walks/ within a minute or two. Bask in the glory briefly — we're not done yet.
You can ask Claude Code to do just about anything during the build phase. Want a dark mode toggle? A smooth-scroll navigation? An animated SVG? Just ask. And when you want to update the site later, just start a new Claude Code session connected to the same repo, make changes, and push again. The more you treat it like a conversation, the better the results. Don't be shy — it doesn't have feelings (yet).
Make sure your main HTML file is called index.html and is in the root of the repository. GitHub Pages looks for that file specifically. If it's named my-cool-site.html or buried in a subfolder, GitHub Pages will serve a 404 and you'll feel very alone.
Your site has a GitHub Pages URL, but yourusername.github.io/good-boy-walks doesn't exactly scream "professional dog walking empire." Let's point a real domain at it.
If you haven't already, add your domain to your Cloudflare account:
goodboywalks.com)ada.ns.cloudflare.com and leo.ns.cloudflare.com)Nameserver changes can take up to 24 hours to propagate, though it's usually much faster. Cloudflare will email you when it's active. Use this time to question whether "Good Boy Walks" is the best name or if you should have gone with "Bark & Stride."
Once Cloudflare is active for your domain, set up the DNS records to point at GitHub Pages.
In your Cloudflare dashboard, go to DNS → Records and add the following:
# CNAME record for the www subdomain
Type: CNAME
Name: www
Target: yourusername.github.io
Proxy: Enabled (orange cloud)
# CNAME record for the apex domain
Type: CNAME
Name: @
Target: yourusername.github.io
Proxy: Enabled (orange cloud)Cloudflare supports CNAME flattening, which means you can use a CNAME record for the apex domain (goodboywalks.com) even though that's technically not allowed by the DNS spec. Cloudflare resolves it automatically. This is simpler than adding four separate A records for GitHub's IP addresses.
Go back to your GitHub repo's Settings → Pages and:
www.goodboywalks.com)This will create a CNAME file in your repo's root containing your domain name. GitHub handles this automatically — no terminal work needed.
One more thing — make sure Cloudflare's SSL settings play nice with GitHub Pages.
Give it a few minutes for everything to propagate. Then visit your domain. Your single-page website — built with Claude Code, hosted on GitHub, served through Cloudflare — is live on the internet. You built this. Well, you and Claude. Mostly Claude. But you were there, and that counts.
Three tools. One browser. Zero installs. Zero context switching into an IDE you don't understand. Go build something.