RobotnixAcademy

Unit 09 · overview

Unit 9: Production Portfolio and Architecture Defense

No new Jekyll feature is the goal here.

This Unit turns the completed portfolio into a production-quality, inspectable artifact and makes you defend the architecture from source to public browser.

Unit question

Can you prove that the portfolio is maintainable, accessible, intentional, reproducible, and traceable from source history to the public deployment?

Unit path

  1. Audit the Portfolio as a System
  2. Content and Public-Identity Review
  3. Accessibility Audit
  4. Performance and Asset Audit
  5. Link and Metadata Audit
  6. Source Hygiene and Generated-File Review
  7. Trace One Page Through the Entire Jekyll Pipeline
  8. Architecture Diagram
  9. Stress-Test the Build
  10. Stress-Test Deployment
  11. Final Revision Set
  12. Prepare the Evidence Dossier
  13. Portfolio Architecture Defense

Final artifact

A published portfolio, source repository, architecture diagram, review-candidate commit, evidence dossier, quality audit, decision records, and architecture defense.

Completion rule

The course is evidence-gated, not calendar-gated. Completion means the learner can build, read, debug, deploy, and explain the site they created.