Unit 04 · overview

Unit 4: Data and Content Systems

This is the largest content-model Unit in the course because Jekyll gives you several ways to represent information.

The point is not to use all of them. The point is to choose intentionally.

Unit question

When should information be a data record, page, post, or collection document, and what does that choice change in the generated site?

Unit path

  1. Content Is Not All the Same Shape
  2. Data Files and site.data
  3. Build a Project Grid from _data
  4. Pages and Generated URLs
  5. Permalinks
  6. url, baseurl, and Safer Link Construction
  7. Posts and Filename Conventions
  8. site.posts, Dates, Categories, and Tags
  9. Build a Technical Project Journal
  10. Collections and Custom Content Types
  11. Define a Project Collection
  12. Collection Documents and Output
  13. Data Files vs Pages vs Posts vs Collections
  14. Debug a Content-Model Failure
  15. Unit Build: Portfolio Content Architecture

Unit artifact

A documented content architecture using pages, structured data, posts, and a project collection where appropriate, plus URL/permalink evidence and one content-model diagnosis.

Upstream foundation

This Unit adapts Jekyll's official Data Files, Blogging, Collections, Pages, Variables, and Permalinks documentation at pinned commit 74d751339d3e534aa51d5d7b0640e9bd743509e4 under the MIT License.