Unit Build: Published Portfolio

Unit 8 ends with a public portfolio tied to inspectable source history and a reproducible deployment path.

Required Git evidence

Show:

• coherent commit history;
• at least one branch-based change;
• one reviewed diff;
• one commit you can explain line-by-line at a high level;
• upstream Jekyll commit reading note.

Required deployment evidence

Show:

Public URL:
Deployed commit:
Publishing mode:
Build/deploy workflow or branch source:
Production build evidence:
Deployment run/status:

Production verification

Test all major routes and asset classes.

At minimum:

Home
About
Projects
Project detail
Journal
CSS
images
navigation
keyboard focus
metadata/title

Failure evidence

Include one local-vs-production incident or controlled equivalent with:

• local observation;
• production observation;
• differing assumption;
• repair;
• redeployment proof.

Deployment architecture diagram

Create your real path:

LOCAL SOURCE
   ↓ git commit
LOCAL REPOSITORY
   ↓ git push
GITHUB REPOSITORY
   ↓ Pages source/workflow
JEKYLL BUILD
   ↓ artifact
PAGES DEPLOYMENT
   ↓
PUBLIC URL

Adjust this to your chosen mode.

Unit defense

Explain:

1. What does Git add that a deployed URL cannot show?
2. Why should you review a diff before committing/merging?
3. What is the difference between Git and GitHub?
4. Why is localhost not deployment evidence?
5. Which Pages publishing mode are you using and why?
6. What commit is currently deployed?
7. How would you identify whether a failure occurred during build, deploy, or generated-site behavior?
8. What production URL/base-path assumption did you verify?

Move on when

The portfolio is publicly reachable and you can prove exactly which source history and deployment path produced it.

Unit 9 is no longer about adding features. It is about production quality and defending the architecture you built.