RobotnixAcademy

Unit 06 · overview

Unit 6: Configuration, Rendering, and Debugging

This is the troubleshooting core of the course.

You will stop treating _config.yml, Liquid, URLs, and generated output as unrelated files and instead read Jekyll as a staged build pipeline.

Unit question

When a Jekyll site fails, what evidence tells you which build, content, configuration, path, or deployment boundary actually failed?

Unit path

  1. _config.yml Is Site-Wide State
  2. Common Configuration Values
  3. Front Matter Defaults
  4. url and baseurl
  5. Development vs Production Environments
  6. The Jekyll Rendering Process
  7. Read Build Output Before Editing Random Files
  8. YAML Failures
  9. Liquid Failures
  10. Path and URL Failures
  11. Configuration Failures
  12. Build a Failure Tree
  13. Broken-Site Diagnostic Lab
  14. Write a Reproducible Bug Report
  15. Unit Build: Configuration and Debugging Evidence Pack

Unit artifact

A documented configuration model, rendering trace, failure tree, multi-family incident evidence, and reproducible bug report.

Upstream foundation

This Unit adapts Jekyll's official Configuration, Rendering Process, Troubleshooting, Variables, Permalinks, and Deployment documentation at pinned commit 74d751339d3e534aa51d5d7b0640e9bd743509e4 under the MIT License.