Unit 8: Git, GitHub, and Deployment

Your Jekyll site is mature enough to become a real public software artifact.

This Unit connects source history, code review, GitHub, production Jekyll builds, GitHub Pages, and public verification into one deployment path.

Unit question

How can another person trace a public portfolio back to the exact source decisions, build, and deployment that produced it?

Unit path

1. Why the Source Repository Matters
2. Initialize and Read Git History
3. Small Commits and Useful Messages
4. Branches
5. Read a Diff
6. Review a Change Before Merging It
7. Read an Upstream Jekyll Commit
8. Local Build Is Not Deployment
9. Production Builds
10. GitHub Pages Architecture
11. Repository and Pages Configuration
12. Publish the Portfolio
13. Production URLs and Base Paths
14. Local-Works / Production-Breaks Lab
15. Deployment Evidence and Recovery
16. Unit Build: Published Portfolio

Unit artifact

A published portfolio tied to Git history, reviewed source changes, deployment architecture, build/deploy evidence, and one production-failure diagnosis.

Source boundary

Jekyll mechanics remain grounded in the pinned upstream repository. GitHub Pages deployment behavior is checked against current official GitHub documentation because Pages workflow/settings evolve independently of the pinned Jekyll source.