Systems Note: Bring the Newsletter Home

Published: 2026-07-13 · Author: Tony Easterling

The newsletter should strengthen the home base, not split the record of the work across places that are hard to maintain. The current direction is an owned archive that sits alongside the builds and blog.

The publishing path

Issues can be represented as structured local data, rendered by the site, and connected to the projects they reference. The publishing flow keeps a distinct draft and approval state, so a useful system can be automated without quietly publishing something that has not been checked.

This also creates a clearer relationship between writing and the work itself. A newsletter issue can point to a test, a release, or a project page without handing the whole history to a third-party archive.

The operational benefit

Owning the path makes it easier to improve. Calls to action, archive presentation, and publishing safeguards are all visible in the same repository as the site. That is a much better place to notice drift and make a small correction.

Lesson learned

Ownership is not about rejecting every external tool. It is about making sure the important record, review step, and public destination remain understandable when those tools change.