Building the Fosterman publishing system

Turning the website from a static artifact into a daily operating system.

What happened

I stopped treating the site as a page that needs to be redesigned every time I have something new to say. It is now a content system: four collections, typed front matter, and pages that assemble themselves from whatever is published.

What I noticed

The old version required a code change for every thought. That is a tax on writing, and a tax on writing is a tax on the whole body of work. The bottleneck was never the design.

What changed in my thinking

A daily update should be one Markdown file. The site should decide where it appears based on metadata, not on where I remember to paste it.

The receipt

This entry was created with the same generator and the same schema that every future entry will use. If the system works, this file is the proof; if it doesn’t, this file is the first thing that breaks.

What comes next

Import the strongest memoir fragments, leadership receipts, Conduit notes, and Staff+ preparation logs — as artifacts, not as new homepage sections.