Sample project
This project exists to be edited – a scaffold with the front matter keys documented in place.
What sets a project apart from a post🔗
Both use the same template, the same list rows and the same card grid. The difference is entirely in the front matter:
| Key | Required? | Where it shows |
|---|---|---|
title | yes | H1, list row, card, browser tab, search results |
description | strongly advised | header lede, row/card excerpt, <meta>, search |
weight | yes (section sorts by it) | ordering only – lower sorts first |
[extra] org | optional | meta line everywhere; replaces the date |
[extra] role | optional | appended after the org, middot-separated |
[extra] period | optional | meta line after the org (“Jan 2026 – Present”) |
taxonomies.tags | optional | chips, tag pages, sidebar filter |
the featured tag | optional | CV page’s “Featured projects” sidebar |
[extra] folders | optional | marks tags as named collections (folders) |
[extra] preview | optional | 16:9 crop in lists, cards and the article hero |
Two layout notes🔗
The cover here is colocated: a folder-based page keeps its assets in the same directory as its index.md, so the whole project can be copied in or out as one unit. A flat .md post instead resolves its preview against the static/ and content/ roots – see the sample post.
Folders and tags behave as in the blog: folders are declared per project, their shared display copy lives in the section’s [extra.tag_meta] table. The sample post walks through it.
Delete me – one scaffold per section is plenty.