Push it live

You made a change and saw it update locally. Now let's close the loop — send it back to GitHub, and watch it go live on Vercel automatically.

Open the Source Control panel

Click the branch icon in the VS Code sidebar (third icon from top), or press ⌘⇧G · Ctrl+Shift+G . You'll see a list of files you changed. Click index.tsx from the list.

See all those red and green lines? That's Git tracking every change you — or your AI — make. Red means removed, green means added. This is how you see exactly what AI changed — so you're always in control.

Commit your changes

1. In the "Message" input box, type a short message describing what you did — something like Update homepage content, or press ✨ to generate one
2. Click the Commit button

Your changes are now saved locally on your machine, but not yet synced to GitHub.

Unlike cloud storage like iCloud or Google Docs, Git doesn't sync automatically — you decide when to commit (save a checkpoint) and when to push (upload it). This gives you full control over what goes live.

Push to GitHub

Click Sync Changes to push your code to GitHub.

That's it — your change is now on GitHub, and Vercel will pick it up automatically.

git add -A
git commit -m "remove placeholder banner"
git push

See it live

Remember the Vercel URL from Chapter 1? Open [your-app].vercel.app — after a minute or so, you'll see your change live.

That's the full cycle: edit → see locally → commit → push. Every change you make from here follows this same flow.

You just leveled up

In Chapter 1, you shipped a site from your browser without writing code. Now you have a real development setup — an editor, a local server, an AI assistant, and a workflow that ships your changes to your website in seconds.

You're not just clicking buttons anymore. You're building.

What's next

You have a real development setup — but your site is still one page with placeholder content.

In Chapter 3, you'll make it yours: multiple pages, real navigation, and a site that looks like something you built.