Module 1 · Build a Website Business · Day 5 of 10

Connect to GitHub so your work is never lost

One laptop crash shouldn't erase five days of work. Today you get a real backup and a real version history.

Video — recording pending, script below stands in for now

Video script (for recording): "This is the day that protects everything else you build in this course. Ten minutes now, and nothing you build again is ever one crash away from gone."

Where you are

Day 01

Install Claude Code, ship your first live page

Day 02

Turn a plain-English idea into a working page

Day 03

Edit what it built — ask for changes without breaking things

Day 04

Understand what got created: files, folders, why they matter

Day 05

Connect to GitHub so your work is never lost

Day 06

Get a site live: your first real deploy

Day 07

Fix things when they break — read errors without panicking

Day 08

Add a second page and link it up: your landing page

Day 09

Automate updates: push once, redeploy every time

Day 10

Ship the deliverable: portfolio + business landing page, live

Why version control matters

Right now, your only copy of this project is on one computer. Git records every change you approve as a checkpoint you can return to; GitHub stores those checkpoints online, so a crashed laptop doesn't mean lost work. This is the safety net every remaining day depends on.

Today's project — get your work backed up

  1. Create a free GitHub account

    At github.com, if you don't already have one.

  2. Ask Claude Code to set up git locally

    Initialize git in this project if it isn't already, and make a first commit with a clear message describing what this project is.
  3. Create an empty repository on GitHub

    Click "New repository" on GitHub, name it something like my-website, and don't initialize it with a README (you already have a project).

  4. Connect and push

    Connect this project to the GitHub repository at [PASTE THE URL GITHUB GAVE YOU] and push it.

    Claude Code will run the actual git remote add / git push commands for you — read what it proposes before approving.

  5. Confirm it worked

    Refresh the GitHub repository page in your browser — your files should now be visible there.