Guardrail: Strict adherence to the Tagging Workflow. Everything defaults to #private. Only notes explicitly tagged #share pass through the publishing filter. Use clear folder structures to separate sensitive data that should never touch the publishing pipeline.
Have this for blog posts, separate folder and explicit status for publishing. A published garden first as a separate folder of cloned notes, then as tagged for publication? Needs a 'touching' process to see diverging note/clone.
Publishing is Pausing: You push a rough idea out to pause your thinking and invite external input.
Like the phrase. Vgl [[Kunst-artefact is (tussen)uitkomst proces 20140505070232]] any artefact is a (intermediate) output of ongoing process. Vgl [[Artefacten uit kennis met methoden 20220215202011]], artefacts brought forth from K through methods.
What Is a Federated Garden? A federated digital garden is a personal knowledge space that: Starts private (your vault, your chaos, your unfinished thoughts) Grows selectively public (some notes bloom into garden pages) Connects across platforms (one source → many destinations) Links bidirectionally (gardens can discover and reference each other) Key principles: Gradual disclosure: Not everything needs to be public—choose what to share Version multiplicity: A note can exist as a draft, a garden page, a newsletter piece, and a toot Decentralized ownership: You control the source, not a platform Interoperability: Uses open standards (Markdown, RSS, ActivityPub, HTML)
The page confuses tools and content imo, but this is a workable list of attributes. 'Grows selectively public' is the key imo. #openvraag #webbeheer What can I do to improve the note to webpage pipeline I have but seldom use?
My goal in this is to treat knowledge as a living, collaborative process, not a series of finished articles.
yes, but 'finished article' never was K. Artefacts may be carriers.
https://web.archive.org/web/20240714180109/https://hyperphor.com/ammdi/Agency-Made-Me-Do-It
Mike Travers site is a wiki more than a blog but not quite a wiki either. It's Logseq based and tied to a self-rolled publishing tool. Also uses Zotero in their stack. Seems he transformed his blog into this garden in Oct 2021.