$ day-1 --pm · demo 3
Deploying to GitHub Pages with Claude Code for Web
Take a project out of the chat window and onto the open web. You will use Claude Code for Web to build your site as real files in a Git repository, then publish it for free with GitHub Pages.
$ demo --account [+][-]
Make sure you have a GitHub account. If you use a .edu email, you can claim GitHub Education benefits (free GitHub Pro), which is worth doing but not required for this demo.
$ demo --repo [+][-]
Create a new repository with a descriptive name—something like sci-fi-recommender or book-recommendation-system—and initialize it with a README file.
$ demo --build [+][-]
Open Claude Code for Web from the Claude sidebar and authorize the GitHub connection. Then build the site one file at a time, which makes iteration far easier:
- Ask for the JSON data file first.
- Then the HTML.
- Then the JavaScript.
- Then the CSS.
Requesting the files separately keeps each change reviewable instead of regenerating everything at once.
$ demo --deploy [+][-]
Accept Claude’s pull request to merge the files into your repository. Then:
- Go to the repository’s Settings → Pages.
- Set the source to Deploy from a branch, using the main branch at the root (
/). - Wait for the build, then open your live URL and test it.
$ demo --reflect [+][-]
Share your deployed GitHub Pages URL and reflect:
- How does working with real files and version control change the workflow compared to a single chat Artifact?
- What did committing through a pull request let you see or undo that an inline edit would not?
- When is the move from a quick Artifact to a deployed, version-controlled site worth the extra steps?
$ source — adapted from Week Eleven: Deploying to GitHub Pages, Humanities & AI. $ cd .. — back to the course packet