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
- Content Is Not All the Same Shape
- Data Files and
site.data - Build a Project Grid from
_data - Pages and Generated URLs
- Permalinks
url,baseurl, and Safer Link Construction- Posts and Filename Conventions
site.posts, Dates, Categories, and Tags- Build a Technical Project Journal
- Collections and Custom Content Types
- Define a Project Collection
- Collection Documents and Output
- Data Files vs Pages vs Posts vs Collections
- Debug a Content-Model Failure
- 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.