Context
Today's May 5 release prompted the question of where version-by-version release content belongs. Aaron's preference is to keep /blog reserved for human/narrative content — low-frequency, high-quality posts that read as essays, not changelogs. Release notes deserve their own home.
PR #28 originally included a /blog/modular-admin-and-agent/ post; it was pulled before merge to preserve the blog's narrative posture.
Sketch
A separate /releases (or /changelog) section of parachute.computer:
- One entry per coordinated release across the ecosystem (e.g., May 5 = "modular admin arc"; April 23 = "launch")
- Per-package version stamps with links to GitHub Releases / CHANGELOGs
- Possibly auto-generated from the per-repo
CHANGELOG.md files (parachute-vault, parachute-hub, parachute-scribe, parachute-notes, parachute-agent, parachute-patterns) at build time
- Linkable from the homepage hero pill (current pill is static, no link target)
- Indexable by version + by date
Open questions
- Manual vs auto-generated. Auto-gen is more maintainable but constrains the format to whatever each repo writes in its CHANGELOG. Manual is editorial but means writing every release in two places.
- Per-package vs per-coordinated-release as the unit. Coordinated-release reads better as a story; per-package reads better for someone tracking a single dependency.
- Whether this lives at
/releases (matches GitHub vocabulary) or /changelog (matches semver/keep-a-changelog convention).
When
Post-pitch. Not urgent — the homepage banner and pitch slide cover the May 5 ship without it. Worth designing once there's time for the structure to settle.
Context
Today's May 5 release prompted the question of where version-by-version release content belongs. Aaron's preference is to keep
/blogreserved for human/narrative content — low-frequency, high-quality posts that read as essays, not changelogs. Release notes deserve their own home.PR #28 originally included a
/blog/modular-admin-and-agent/post; it was pulled before merge to preserve the blog's narrative posture.Sketch
A separate
/releases(or/changelog) section of parachute.computer:CHANGELOG.mdfiles (parachute-vault, parachute-hub, parachute-scribe, parachute-notes, parachute-agent, parachute-patterns) at build timeOpen questions
/releases(matches GitHub vocabulary) or/changelog(matches semver/keep-a-changelog convention).When
Post-pitch. Not urgent — the homepage banner and pitch slide cover the May 5 ship without it. Worth designing once there's time for the structure to settle.