Public course syllabus
Jekyll: For Students
Build one portfolio from a blank folder to a tested, published Jekyll site while learning how the generator actually works. Students trace source files through Jekyll's rendering/build process, use Markdown, YAML front matter, Liquid, layouts, includes, data files, pages, posts, collections, assets, configuration, themes, plugins, Git, and deployment. They repeatedly debug controlled failures, verify generated output, make accessibility/privacy decisions, and finish by defending the site's architecture from source repository to production browser. The course is self-paced and organized as nine learner-facing Units.
Course overview
This self-paced course builds a real Jekyll portfolio from a blank folder to a tested, published site. Learners trace Markdown, YAML front matter, Liquid, layouts, includes, data, pages, posts, collections, assets, configuration, themes, plugins, Git, deployment, accessibility, privacy, and failure recovery.
Audience and pace
Grades 9–12. Nine evidence-gated Units have no calendar deadlines; move forward when the build and verification evidence is complete.
What you will learn
- Explain how source files move through Jekyll’s rendering and build process into a published site.
- Choose content models, reusable templates, configuration, themes, plugins, and deployment paths intentionally.
- Debug controlled failures, verify generated output, and defend accessibility/privacy decisions.
Course structure
Units cover foundations/build; Markdown/front matter/Liquid; layouts/includes; data/content systems; assets/CSS/accessibility; configuration/debugging; themes/plugins; Git/deployment; and final production review.
Learning evidence and assessment
Learners build one portfolio, retain source and generated-output evidence, debug controlled failures, use Git history, perform audits, and document architecture decisions.
Expectations and boundaries
Use approved repositories and publishing environments. Do not expose personal information, publish unreviewed work, copy themes/plugins without following licenses, or treat a successful build as proof of accessibility or deployment correctness.
Capstone
Portfolio Architecture and Defense explains source structure, templates, content model, output, Git, deployment, accessibility/privacy, one controlled failure diagnosis, and tradeoffs.
Access and support
The course provides structured reader guidance. Local Ruby/Jekyll and deployment work follow the approved environment instructions; analysis alternatives are available while setup is in progress.