I first start a discussion based on my org-roam publishing needs on how-to section of this discourse (Advice on Roam workflow, how do you separate private and public part of your garden?), but after some reflexions and one enhancement issue open on github (https://github.com/org-roam/org-roam/issues/911) i think we could generalize the idea, starting from simple workflow to complex workflow for publishing digital garden on the web.
Lot of discussions about org / org-roam are note-taking-workflows or note-publishing-workflows discussions. As you know, there are probably more of these workflows than peoples on earth, so we don’t try to encapsulate all of them in this post.
I propose you to define some classic publishing note taking and note publishing workflow.
IMHO that could also help org beginer. It’s easier to start publishing note with a template in mind.
Like @jethro say, this is out of scope for org-roam core, and we probably need to create a specific
Objectives of the package :
- generate a template based on simple or complex use-case already defined
- managing/preparing org-roam note for multiple front-end : ox-hugo, firn, etc.
- use filter rules to select which org notes are published (or not) for which front end
- simple workflows :
- one db, one website, all notes
- complex workflows :
- one db, multiple website, filtering by taf and private/public note
- multiple db, multiple website, filtering by tag and private/public note
Because i think it’s more easy to represent workflow using schema, i try to represent one of the complex publishing workflow in this schema. The svg is also shared, if you want to propose new things based on this first work.
In this workflow :
- work & home could be defined by
- we have private (gpg) and public not in HOME and WORK context
- we have two publishing platform and three website
- one website publish/contain only public note from WORK context
- one website publish/contain only public note from HOME
- one website publish/contain only private note from HOME
I think we could add one more level of filtering, because an user might want to publish only “note” marked as “ok-to-be-published” and not publish “draft”.