RobotnixAcademy

Unit 09 · lesson

Prepare the Evidence Dossier

The portfolio itself is one artifact.

Your evidence dossier proves you understand how it works.

Required sections

1. Project identity

  • purpose;
  • intended audience;
  • public/privacy boundary.

2. Source architecture

  • project tree;
  • content models;
  • layouts/includes;
  • configuration/dependencies.

3. Build architecture

  • Jekyll rendering trace;
  • one page source → output trace;
  • generated _site evidence.

4. Version history

  • review-candidate commit;
  • meaningful commit examples;
  • one branch/diff/review example.

5. Deployment

  • public URL;
  • Pages publishing model;
  • workflow/deployment evidence;
  • production URL/base-path strategy.

6. Quality

  • accessibility findings;
  • responsive evidence;
  • performance/asset finding;
  • privacy/publication decision;
  • link/metadata checks.

7. Failure and recovery

  • one build failure;
  • one production/deployment or path failure;
  • failure tree/diagnosis;
  • recovery plan.

8. Decisions

Include at least two ADR-style decisions, for example:

  • project collection vs data file;
  • custom layouts vs theme;
  • plugin accepted/rejected;
  • deployment mode.

Evidence beats screenshots without context

A screenshot that says "it worked" is weak.

Pair evidence with:

claim
source/state
observation
why it proves the claim

Checkpoint

Give the dossier to someone who has not built your site. They should be able to understand the architecture before you explain it aloud.