The archive stays broad enough to feel real and narrow enough to remain useful.
Each page sits inside one of three tracks: active systems practice, design observations, or field documentation from actual working sessions.
Systems practice
Notes on infrastructure, service layouts, operational defaults, and the small adjustments that make recurring work less brittle.
Browse case filesInterface study
Short evaluations of layouts, information density, wayfinding, and the visual cues that let a site feel maintained rather than abandoned.
See the guidebookNight fieldwork
Lightweight dispatches collected from evening sessions, city walks, and the kinds of observations that only become visible once the daytime noise has thinned out.
Read dispatches
A field-tested pattern for low-noise publishing stacks
The current case file follows a very specific question: what happens when a publishing stack is designed around calm maintenance instead of feature accumulation? The answer lives in tooling choices, naming rules, and a bias toward outputs that can be inspected without a dashboard.
- Prefer assets that can be copied and served directly
- Keep the visible surface broader than the operational core
- Publish enough cross-links that the archive looks lived-in
A fuller site needs visible movement, not just a hero section.
Dispatches from the quiet hours
Short entries on cadence, context, and what small systems reveal late at night.
Open journal index
Ways to follow the archive
Open notes, focused digests, and workshop-style reviews for selected case files.
See programs
Shelf notes and recurring references
A reading list of books, tools, and manuals that continue to influence the archive.
Visit the libraryThe archive is intentionally denser than a landing page.
A convincing static site needs side streets: enough linked material, enough dated pages, and enough variation in format that a visitor can wander without immediately hitting the edge of the set.