I had a thought that might work really nicely if it’s done correctly.

Imagine you have a project. You make changes to it. You cut releases. That’s all normal. But as far as I know, there isn’t really a release mechanism built into Tangled. I could be wrong about that, but I don’t think there’s anything formal there.

That got me thinking about whether releases could just be modeled differently instead of adding some entirely separate system.

Releases as standard.site documents

What if releases were implemented as a form of standard.site document?

Instead of treating releases as some special, external concept, they could just be documents like anything else—structured, publishable, and discussable. A release would essentially be a document that represents a specific version of a project.

That feels kind of clean to me. It doesn’t invent a new primitive. It just reuses the document model.

Publications for repositories with releases

If a repository has releases, maybe it could have its own publication.

People could subscribe to that publication as a way of subscribing to the releases for that project. Each new release document would just flow through that publication. There’d be a natural place to discuss it, react to it, and follow along.

It’s not a fully formed idea. I don’t really have all the edges worked out. But the core thought is simple: put open source project release information into standard.site documents and let the existing publishing and subscription model handle the rest.

That’s kind of the whole idea for now.