Trevor PaughSystems engineer
Trevor PaughProject Chronicles

Chronicles / Project Chronicles

Active · Oct 2026 to present

Project Chronicles

This site. A public history of every project, written by a historian session that reads the repos and takes notes from the managers.

10 entries Stack Astro 5 · Content collections · Cloudflare Workers · GitHub · Pillow trevorpaugh.com/chronicles View on timeline

Project Chronicles is the working history of the owner's software projects, published under trevorpaugh.com/chronicles. One section per project, each entry a dated milestone, design change, decision, or progress note, written to read like a designer's and developer's blog rather than a changelog.

It is maintained by a dedicated Claude session, the historian, which polls each project's git history daily and takes short notes from the project managers when git records what changed but not why. Everything is backfilled from the repos first, then kept current.

The site is a static Astro build, served from Cloudflare Workers as part of the owner's home page since 8 October: a board of projects on the home page, a magazine-style landing per project, and one timeline across everything with filters. Four colour schemes, picked from the OS light or dark setting. It is also, naturally, a project in its own history.

Latest developments

Progress

A capture, every time

The brief that project managers follow when they write to the historian now asks for a screenshot or mockup of anything visual, every time, saved under the project's own captures folder and listed on a Capture line in the note. The historian decides what to use.

Milestone

A home page around the Chronicles

The wrapper landed the same day as the move: a sidebar with Home, Chronicles, CV, and Profile, a magazine-style home page with three featured projects and the five newest entries, and two themes, Fieldnotes and Darkroom, chosen by the owner out of the Chronicles' four. The type is IBM Plex, self-hosted so the site makes no third-party requests. The Chronicles pages keep their old look until the next slice restyles them to match.

Milestone

The Chronicles move under the home page

Four days after its first deploy, the site changed address and repository. The owner decided the Chronicles should live under a personal home page rather than be the whole of trevorpaugh.com, so the repo was imported, history intact, into a new one for the home page, every page moved under /chronicles, and hosting moved from Cloudflare Pages to Workers static assets. The historian took its own worktree on main and the old repository was archived.

Design

One site, two themes

The third slice of the day brought every Chronicles page inside the home-page wrapper. The landing is now a board that ranks projects by their last thirty days of activity, with a tick per day, beside a feed of recent entries. The four colour schemes, their picker, and the launch-day type are gone; the whole site shares one set of colour tokens under Fieldnotes and Darkroom, and a visitor's old scheme choice is carried over once.

Milestone

trevorpaugh.com is live

Planning finished in the morning and the site launched before the day was out. The domain and its www twin now point at the new home page, with the Chronicles at /chronicles and the feed under it. Four slices shipped in a day: the import with history, the wrapper and home page, the restyle, and launch preparation. The bio on the profile page is a draft; the owner's contact links stay hidden until confirmed.

Design

A heading font that hurt to read

Darkroom's headings were set in Syne at its heaviest weight, which stretches very wide. The owner called it painful. It was swapped for Space Grotesk within the hour.

Decision

How the historian learns things

No daily reports from the managers. The historian polls every project repo once a day, takes a five-line note straight from a project's manager when git records what but not why, and keeps a public register: no other people's names, no earnings, no prices under discussion, no keys.

Milestone

Live on trevorpaugh.com, with 39 entries backfilled

The first build: an Astro static site with six projects and 39 entries read out of the repos, four colour schemes, a timeline with animated filters, pushed to GitHub and served by Cloudflare Pages on the owner's domain.

Design

Screenshots, with the sensitive parts blacked out

The Clipper app screenshots and the Permit landing mockup were held back from the first build. The owner cleared them on one condition: handles, channel names, and anything with a dollar sign get redacted. Solid boxes, not blur, and the pricing section cropped away.

Decision

The brief: a public history, one section per project

The owner asked for a site that holds the history of all their projects and work, and picked from a round of mockups: a board for the home page, magazine landings per project, one filterable timeline, and all four colour schemes kept.

The story, from the beginning

The brief: a public history, one section per project

The owner asked for a site that holds the history of all their projects and work, and picked from a round of mockups: a board for the home page, magazine landings per project, one filterable timeline, and all four colour schemes kept.

Read the entry
You're responsible for building a website that will host the history of all my projects and work.

Screenshots, with the sensitive parts blacked out

The Clipper app screenshots and the Permit landing mockup were held back from the first build. The owner cleared them on one condition: handles, channel names, and anything with a dollar sign get redacted. Solid boxes, not blur, and the pricing section cropped away.

Read the entry
Blur out/redact handles, channel names, and anything with $$$. Redact proposed price tiers.
A redacted Clipper Health page: the channel name and the spend figures are solid blocks.
A redacted Clipper Health page: the channel name and the spend figures are solid blocks.

Live on trevorpaugh.com, with 39 entries backfilled

The first build: an Astro static site with six projects and 39 entries read out of the repos, four colour schemes, a timeline with animated filters, pushed to GitHub and served by Cloudflare Pages on the owner's domain.

Read the entry
The board on launch day, in Darkroom.
The board on launch day, in Darkroom.

How the historian learns things

No daily reports from the managers. The historian polls every project repo once a day, takes a five-line note straight from a project's manager when git records what but not why, and keeps a public register: no other people's names, no earnings, no prices under discussion, no keys.

Read the entry

A heading font that hurt to read

Darkroom's headings were set in Syne at its heaviest weight, which stretches very wide. The owner called it painful. It was swapped for Space Grotesk within the hour.

Read the entry
This particular font is painful to read.

trevorpaugh.com is live

Planning finished in the morning and the site launched before the day was out. The domain and its www twin now point at the new home page, with the Chronicles at /chronicles and the feed under it. Four slices shipped in a day: the import with history, the wrapper and home page, the restyle, and launch preparation. The bio on the profile page is a draft; the owner's contact links stay hidden until confirmed.

Read the entry
Draft the bio, go.

One site, two themes

The third slice of the day brought every Chronicles page inside the home-page wrapper. The landing is now a board that ranks projects by their last thirty days of activity, with a tick per day, beside a feed of recent entries. The four colour schemes, their picker, and the launch-day type are gone; the whole site shares one set of colour tokens under Fieldnotes and Darkroom, and a visitor's old scheme choice is carried over once.

Read the entry
Seamless home and Chronicles, nothing lost.
The new board under /chronicles, in Darkroom, a few hours after the wrapper landed.
The new board under /chronicles, in Darkroom, a few hours after the wrapper landed.

The Chronicles move under the home page

Four days after its first deploy, the site changed address and repository. The owner decided the Chronicles should live under a personal home page rather than be the whole of trevorpaugh.com, so the repo was imported, history intact, into a new one for the home page, every page moved under /chronicles, and hosting moved from Cloudflare Pages to Workers static assets. The historian took its own worktree on main and the old repository was archived.

Read the entry
Only once the new repo is in place and the historian is aware and using it will the historian take care of archiving the old chronicles repo.

A home page around the Chronicles

The wrapper landed the same day as the move: a sidebar with Home, Chronicles, CV, and Profile, a magazine-style home page with three featured projects and the five newest entries, and two themes, Fieldnotes and Darkroom, chosen by the owner out of the Chronicles' four. The type is IBM Plex, self-hosted so the site makes no third-party requests. The Chronicles pages keep their old look until the next slice restyles them to match.

Read the entry
The names of the themes from the Project Chronicles that I like are Dark Room and Field Notes.
The new home page in Darkroom, on the day it landed.
The new home page in Darkroom, on the day it landed.

A capture, every time

The brief that project managers follow when they write to the historian now asks for a screenshot or mockup of anything visual, every time, saved under the project's own captures folder and listed on a Capture line in the note. The historian decides what to use.

Read the entry