Is digital garden a creation/curation style, design pattern, or an arcgitecture that fits some platforms better than others? Thoughts etc?
I covered static sites in my text renaissance post but not digital gardens since I don’t yet have a sense of it
Conversation
1/ I've been thinking of it very much as a pattern language centred around the core ethos of non-chronoloigcal WIP microposts.
Layered with a pick n' mix set of common design patterns;
Wikis
Unsorted piles
Exploratory node graph
Internal Bi-directional links
1
1
20
2/ External Bi-directional links (web mentions)
Invitiations to collaborate (edit buttons, quick links to tweet backs)
Annotation a la
Heavy reposts, citations, credits, & references
Changelogs (or alternatively, complete chronological abstinence)
3
1
9
3/ You pick the patterns that best fit your content
General experimentation with the medium of the web feels like it has a strong role here too.
Resurgence of playful, weird CSS.
Tools like reducing friction for mixing interactive elements into text.
1
1
5
4/ So far SSG's like , Next.js, (and whatever magic is building ;)), are the best medium for the R&D efforts of the Twittering Digital Gardeners Association™️
Once we settle into a few design patterns that work well for the majority...
For me the notion of the “digital garden” is a metaphor on the work more than any sort of technical implementation or specification.
The fight against entropy. The personality and character of the gardener reflected in the garden.
Community gardening. 🌱
1
7
Show replies
5/ ...expect we'll land on a few core implementations for various platforms. Easier to build the thing with well-tested UX patterns to go off.
Might simply look like well-made and well-documented Gatsby / Ghost / Tiddlywiki/ etc. themes.
1
2
Why would you say that a SSG is better than just a SPA? Curious because I started building static with Vuepress but I’m second guessing that decision now.