Set up once. Then every build is a chat.

It's where you describe what you want and Claude makes it. The Free plan covers every guide on this site; Pro adds the shortcut where Claude saves changes to GitHub itself.

1. Go to claude.ai and sign up with your email address or a Google account.
2. That puts you on the Free plan. You can chat on the web, on a computer or on your phone.
3. You can attach pictures to a message, such as a screenshot of a website you like (up to 20 files per chat).

What you'll see: A chat box. Everything in the guides starts by typing in it.

A website is a handful of files. With this switched on, Claude can make them and give them to you to download, ready to upload to GitHub.

1. In Claude, open Settings, then Capabilities.
2. Switch on "Code execution and file creation". It is available on the Free plan.
3. When Claude has made your files, download each one into a single folder on your computer.

What you'll see: A list of capabilities with switches. The one you want is "Code execution and file creation".

A repository is a folder on GitHub that keeps every version of your files. It's the one place your site lives: you (or Claude) change the files there, and Cloudflare publishes whatever is in it.

1. Sign up at github.com. The Free plan is enough.
2. Select + at the top right of any page, then New repository.
3. Type a short name, such as toms-towpath-walks. Switch "Add README" on, so the repository isn't completely empty (Cloudflare needs something in it to connect to).
4. Select Create repository.

What you'll see: Your new repository with one file in it, README.md. That file never shows on your website.

Cloudflare is where your site is live on the internet. Once it is connected to your repository, every change to the files on GitHub goes live by itself, in a minute or two. A site made of plain files costs nothing to host: Cloudflare says requests to static files are "free and unlimited".

1. Sign up at dash.cloudflare.com/sign-up and confirm your email address.
2. For a website made of plain files (most builds here): in the Cloudflare dashboard, go to Workers & Pages, select Create application, then Pages, then Connect to Git. For the chatbot, the app and the dashboard, stop after signing up: their guides connect Cloudflare after your first upload.
3. Sign in to GitHub when asked and let Cloudflare see your repository (Install & Authorize). Pick the repository, then Begin setup.
4. Leave the production branch as main and the build command blank. Select Save and Deploy.
5. Your site's address is your-project-name.pages.dev. Until you upload your files it has nothing to show; after that, every change you commit on GitHub redeploys it.

What you'll see: A Cloudflare project that lists its deployments, each with the GitHub change that started it.

So Claude can read the files that are live now before it changes them, even in a brand new chat. On Pro, the same connection is what lets Claude Code on the web save its changes to your repository.

1. In Claude, go to Customize, then Connectors, select GitHub Integration, then Connect, and sign in to GitHub.
2. In a chat, select + at the bottom left, then Add from GitHub, pick your repository and select Add repository.
3. If your repository is private, Claude asks for access to it the first time: follow its link to GitHub and allow it.

What you'll see: GitHub listed under your connectors, and "Add from GitHub" in the + menu of a chat.

What we typed: "I've just done a new walk, so please add it as my latest one on my website: Kintbury to Great Bedwyn. Starts at Kintbury station and finishes at Great Bedwyn Wharf. About 8 miles, roughly 3 hours. Good for: dogs, tea room halfway. My note: "Quiet water meadows, the Dun aqueduct and a heron that followed me for a mile." I'm not technical. When you've finished, tell me in plain English what you changed and what I need to do so it goes live on my website."

• Claude changed two files, walks.html and index.html: the walk went to the top of both pages with the note word for word, and the count became "6 walks so far". It dated the walk 1 October 2026 because we hadn't given a date, and said so.
• It saved the change on a new branch, claude/add-kintbury-walk-oj795y, not on main, and said plainly: "it isn't on your live site yet". Then it gave three clicks on GitHub: Compare & pull request, Create pull request, then Merge pull request and Confirm merge.
• We made the pull request and merged it, as a reader would. The main branch then held exactly Claude's change, which is what Cloudflare publishes.

Read Claude's whole reply, unedited.