About

How this site works

Project Chronicles is the running history of the software I build. Each project has its own section: a magazine-style landing page that tells the story from the beginning, and one page per entry. The timeline puts every entry from every project on one spine, with filters so you can follow one project or compare several.

Right now it covers 10 projects and 141 entries.

Four kinds of entry

• Milestone. Something shipped, launched, or crossed a line: first working version, first deploy, a feature opened to the public.
• Design. A visible change in how something looks or behaves, and the reason it changed.
• Decision. A fork in the road and which way it went: a stack choice, a scope cut, a rule adopted.
• Progress. Steady work that is worth noting without being a single event: a week of tuning, a run of fixes, a migration in flight.

Where entries come from

Most of this history is reconstructed from the repos themselves: commit messages, pull requests, design notes, and the working logs kept alongside the code. Newer entries are written as things happen. The site is kept by a historian role that polls each project's git history on a schedule and writes up what changed, and project managers send a few lines when a decision or a design change needs context that a commit log cannot carry.

Everything here is written for a public audience. Credentials, account identifiers, private contacts, and anything commercially sensitive stay out.

Colour schemes

There are two, shared with the rest of trevorpaugh.com. The site follows your system: Fieldnotes if it prefers light, Darkroom if it prefers dark, and Darkroom if it cannot tell. The theme switch in the sidebar (top right on a phone) flips between them, and your pick is remembered in this browser.

Under the hood

A static site built with Astro. Projects are JSON files and entries are Markdown with front matter, so adding history is a matter of adding a file.

There is an RSS feed of all entries.