In Hubzilla's Cards system I've assembled some links to Digital Gardening.
I think the Cards system itself, which can be used to compile links and place these in categories, is a powerful, probably neglected, feature of Hubzilla that illustrates its distinct advantage over a simple chronological system (although admittedly, the items themselves end up being placed chronologically rather than one I might choose).
One of the articles bookmarked, which is apparently considered to be ground-breaking and formative in the history of digital gardens, is The Garden and the Stream: A Technopastoral by Mike Caulfield. He makes there a powerful argument for the digital gardening style of web publishing instead of the reverse-chronological form that has dominated the web since blogging and micro-blogging platforms took over much of it, as a means to assemble and broaden knowledge.
Intrinsic to the metaphor is the idea that rather than present "finished pieces" in the manner of published works, digital gardening aims to gradually improve upon what one has written, in response to further thought, new knowledge, or the integration of valid criticism. An article that speaks of this is Digital Garden Terms of Service (by Shawn Wang).
In a post by Anne-Laure Le Cunff, various tools are mentioned for the creation of digital gardens: for non-technical people: Obsidian Publish, Public Roam Database, Notion, Tiddlywiki, Mental Nodes. For more technical people, Jeykyll, Eleventy, Gatsby and static site builders are suggested.
Although it is never mentioned among the sites that I've found, Hubzilla too places at our disposal various tools that can facilitate digital gardening. As I have often said on Hubzilla, these are quite adequate. Yet they deserve to be further developed, alongside the "stream" model (which even Mike Caulfield admits has its place).
One of Hubzilla's still under-used advantages is that it could harness its community base to establish shared wikis. Till now, my still fledgling Hubzilla wikis have been publicly readable, but written only by me. Responsibility for these could be shared and it would be great to see further community efforts.
I think the Cards system itself, which can be used to compile links and place these in categories, is a powerful, probably neglected, feature of Hubzilla that illustrates its distinct advantage over a simple chronological system (although admittedly, the items themselves end up being placed chronologically rather than one I might choose).
One of the articles bookmarked, which is apparently considered to be ground-breaking and formative in the history of digital gardens, is The Garden and the Stream: A Technopastoral by Mike Caulfield. He makes there a powerful argument for the digital gardening style of web publishing instead of the reverse-chronological form that has dominated the web since blogging and micro-blogging platforms took over much of it, as a means to assemble and broaden knowledge.
Intrinsic to the metaphor is the idea that rather than present "finished pieces" in the manner of published works, digital gardening aims to gradually improve upon what one has written, in response to further thought, new knowledge, or the integration of valid criticism. An article that speaks of this is Digital Garden Terms of Service (by Shawn Wang).
In a post by Anne-Laure Le Cunff, various tools are mentioned for the creation of digital gardens: for non-technical people: Obsidian Publish, Public Roam Database, Notion, Tiddlywiki, Mental Nodes. For more technical people, Jeykyll, Eleventy, Gatsby and static site builders are suggested.
Although it is never mentioned among the sites that I've found, Hubzilla too places at our disposal various tools that can facilitate digital gardening. As I have often said on Hubzilla, these are quite adequate. Yet they deserve to be further developed, alongside the "stream" model (which even Mike Caulfield admits has its place).
One of Hubzilla's still under-used advantages is that it could harness its community base to establish shared wikis. Till now, my still fledgling Hubzilla wikis have been publicly readable, but written only by me. Responsibility for these could be shared and it would be great to see further community efforts.