Optional — a snapshot in time (Git idea)

Git is not required for your capstone. This lesson is concept + one optional action so you know what people mean by “commit.”

Concept — two ways to undo

Approach	What it is	Good when
Copy the folder	Duplicate my-static-site → my-static-site-backup	Quick safety before big experiments
Git commit	A named snapshot of files in that folder	You want dated checkpoints and smaller diffs

Commit (simple picture) = “Save game” for your project. Branch = optional side path—ignore for now.

Do this — pick your path (5 minutes)

Path A — No Git yet (totally fine)

1. Duplicate your project folder in the file manager.
2. Rename the copy my-static-site-before-css-experiment (or similar).

You now have a rollback if you break something.

Path B — Git already installed and allowed

Only if you already use Git and your policy allows it:

1. Open a terminal in my-static-site.
2. Run:

git init
git add .
git commit -m "Initial static site lesson"

3. Change one line in index.html, then:

git diff

Read the diff—you are reading change, which is a professional skill.

If any step fails, stop and stay on Path A.

Practice — two sentences

Answer in two sentences:

1. When would a folder copy be enough?
2. When might Git history earn its complexity?

Example angle: solo hobby vs team handoff vs many experiments.

Check

• You can explain “commit” to a teammate in one plain sentence.
• You chose Path A or B without guilt—optional means optional.

Key takeaways

• Backups and Git both reduce fear of trying ideas.
• This course’s capstone does not require Git; organisation does.

What’s next

Next up: Module 02 check-in