Going Live

Time to put your project on the internet. You already installed Git back in the first lesson, so here you'll configure it, connect GitHub to Claude, push your code, and deploy to Vercel – and from then on, every change you push goes live automatically. Claude does the hands‑on work; you make the decisions.

1. Configure Git with your identity

Git stamps every commit with an author name and email. Set these to the name and the email you'll use for GitHub (next step), so your commits link to your account.

Set up my Git identity
Check my current Git configuration (git config user.name and user.email).
Ask me for the name and email I want on my commits – I'll use the same email for my GitHub account, so they link up. Then set them for me, and confirm what's configured.

Outcome: Git is configured with the name and email you'll use for GitHub.

I configured Git with my name and GitHub email

2. Make your first commit

A commit is a saved snapshot of your project. Let Claude create a clean .gitignore (so secrets and build files stay out) and make your first commit.

Create my first commit
Get my project ready for version control and make the first commit:
1.Make sure the project is a Git repo (initialize it if it isn't already).
2.Create or update a .gitignore for a Next.js project (exclude node_modules, .next, .vercel, and all .env files).
3.Show me what will be included, then make a first commit with a clear message like "Initial project setup".
4.Confirm the commit was created.
Keep this local for now – we'll connect to GitHub next.

Outcome: Your project's first snapshot is committed locally, with secrets and build files safely ignored.

I made my first commit

3. Create your GitHub account

GitHub stores your code online – it's your backup and what Vercel deploys from.

  • Go to github.com and sign up for a free account.
  • Use the same email you set in your Git config above, so your commits are linked to you.

Outcome: You have a GitHub account, ready to host your code.

I created my GitHub account

4. Connect GitHub to Claude

So Claude can create your repository and push your code for you, connect GitHub to the Claude desktop app:

  • Click the + next to the prompt box, choose Connectors, add the GitHub connector, and authorize it (sign in to GitHub when prompted).
Not using Claude Desktop?

If you're working somewhere without the connector (a different tool, or the command line), the GitHub CLI is the fallback: run gh auth login and gh auth setup-git once, and Git can push to GitHub for you. For this course we stay in the Claude desktop app.

Outcome: Claude is connected to your GitHub account.

I connected GitHub to Claude

5. Create your repository and push

Now have Claude create a private repository and push your first commit to it.

Create a private repo and push my code
Using my connected GitHub account:
1.Create a new **private** repository for this project (match the repo name to my project).
2.Connect my local project to it as the "origin" remote.
3.Push my first commit up to GitHub.
4.Confirm my code is now visible in the repository.
If you hit an authentication step, walk me through it in plain language.

Outcome: Your code is safely stored in a private GitHub repository.

I pushed my code to a private GitHub repo

6. Deploy to Vercel

Vercel turns your GitHub repo into a live website and redeploys it automatically every time you push.

  • Go to vercel.com and sign up using your GitHub account – this links the two for you.
  • Import your project's repository. Because it's private, you'll be asked to install Vercel's GitHub app and grant it access to that repo – choose your repository when prompted.
  • Deploy. Vercel gives you a live URL you can share.
Private repo access

Private repos don't deploy until you grant Vercel access. When importing, pick "Only select repositories" and choose this project – then Vercel can build it.

Outcome: Your project is live on the internet at a Vercel URL.

I deployed my project live on Vercel

7. Change, push, watch it go live

Here's the loop you'll repeat forever: make a change, commit, push – and Vercel deploys it in a minute or two. Let Claude run it with you once.

Ship a change end to end
Let's run the full publish loop together:
1.Make a small, visible change to my home page (like improving the headline).
2.Commit it with a clear message and push it to GitHub.
3.Tell me how to watch the deployment in Vercel.
4.Once it's live, confirm the change shows up on my Vercel URL.
Explain the cycle so I understand: change → commit → push → automatic deploy.

Outcome: You updated your live site by pushing a change, and you understand the everyday publish loop.

I can update my live site by pushing changes