really, the issue is that i am not part of a collective
a good software collective is established with two primary goals :—
1. creating good software
2. generating a public record of documents which demonstrate the process of making good software
considering this, one might be forgiven for thinking that there must exist an overabundance of tools for generating and proliferating documentation on the creation of software. after all, this is a problem that every good software collective must solve. however,
@gaditb no, never heard of them
@Lady Oh!
Okay gimme a sec to grab some links.
Do you prefer FOSDEM talk (aesthetically highly based on Legend of Zelda, primarily about their design approach/goals and how it informed their spec-writing),
protocol specs,
protocol conceptual documentation,
example application (running but still hacky and using only a scarce few of the features in their design-space),
or collective devlog/shared blog of how things are more generally?
or fediverse handle of one of the people in it, I guess.
(... grabbing...)
@gaditb oh i mean i would say i care most about whatever most speaks to you, or whatever you think most speaks to me, or something socially contingent along those lines
@Lady
Main site / devlog+ : https://worm-blossom.org
Projects page: https://worm-blossom.org/projects/
"Willow": Data Model/Protocol that is their primary output/locus-point of effort: https://willowprotocol.org
(Has data model explainer, protocol specs, links to their other spec-work this builds on)
"Sneakerweb": Application built on it, intended to build an experience approaching zines, uses directories of HTML. Uses their Willow (Willow '25 specifically) for serialization and for authenticated updates to prior content.
https://sneakerweb.org
FOSDEM talk: "Willow - Protocols for an uncertain future"
https://fosdem.org/2026/schedule/event/CVGZAV-willow/
@Lady Specifically relevant to their documentation (copying descriptions straight from their Projects page)::
WebTT: Lightweight tooltips for the web, without any server-side logic.
https://worm-blossom.org/webtt
Macromania: A macro-based system for generating plaintext files, including this very website.
https://codeberg.org/macromania/macromania
(Maybe there's more of their process/tooling available/documented but I don't know?)
@Lady (... I'll be honest frankly I based on their aesthetics/approach/ideology I think I assumed you must have known about them before I did,
or possibly been indirectly involved.)
@Lady (I think probably you will either go for one or the other -- or switch off both, I don't know how you process attention -- of their devlog+ [ https://worm-blossom.org ], immersing linearly in the way they approach themselves & their process & what-happens-alongside-thst-informs-it (if you want to go fully this route they have their archive forward-chronological from the beginning: https://worm-blossom.org/archive/full/ )
and the Willow data model & spec documentation, exploring network-ly from the Start Here overview of the data model: https://willowprotocol.org/specs/data-model/index.html#data_model )
(I don't know how you feel about video-of-conference-talk-as-way-of-intro, but maybe that ~20min talk. That was my first intro and set a solid base.)
(I think the thing it took me longest to grasp in the concepts was the time/authority/data-path 3D axes they kept drawing in their visualizations. That it was those 3 axes (.. I'm pretty sure), and why it was meaningful they were independent.)
@Lady (You have an eye on what Worm Blossem is doing, right?)
(Both in terms of "software collectives, and documentation", and in terms of "sharing documents".)