RobotnixAcademy

Unit 06 · lesson

Unit Build: Configuration and Debugging Evidence Pack

Unit 6 is complete when you can diagnose the build as a pipeline instead of treating Jekyll as one black box.

Required configuration evidence

Document your current:

  • site identity values;
  • url;
  • baseurl;
  • collections;
  • front-matter defaults;
  • environment-dependent behavior if any;
  • plugin list if already introduced.

Rendering trace

Choose one project page and trace:

source document
→ Liquid
→ Markdown converter
→ project layout
→ default layout
→ destination file

Adjust the trace to match your real source and file type.

Failure tree

Submit your Jekyll failure tree with evidence actions at each branch.

Incident evidence

Include at least three different failure families:

  • parser/build failure;
  • content/path/config failure with successful build;
  • development/production or browser/deployment failure.

Reproducible bug report

Include one minimized bug report from Lesson 14.

Unit defense

Explain:

  1. Why can _config.yml create site-wide failures?
  2. What do front-matter defaults centralize?
  3. Why do url and baseurl matter?
  4. What is one intentional development/production difference?
  5. In what order does Jekyll render Liquid, conversion, and layouts for an applicable page?
  6. Why does a successful build not prove links/content are correct?
  7. How do you distinguish YAML syntax failure from a valid-but-wrong key?
  8. What makes a bug report reproducible?

Move on when

You can start with a symptom, choose the next evidence, and explain why that evidence narrows the failure.

Unit 7 will add themes/plugins — new abstractions and new dependencies that you should only accept when they earn their complexity.