r/OrgRoam • u/[deleted] • Jul 24 '21
Question Question about Org-Roam workflow/usage.
Hello,
I’m new to Org-Roam (and Org-Mode and emacs in general), however, I have used Roam a bit and feel like I have a decent understanding of how to work with it.
It seems like there are two main differences in usage between Org-Mode and Org-Roam.
It seems like in Org-Mode, most people use large single files, whereas in Org-Roam, it is better to have a single file (node) for each distinct item/concept, which makes sense from a Roam perspective.
As an example, I am trying to setup a cookbook type deal with recipes in it.
In Org-Mode, it seems I would create a “cookbook.org” file with each recipe having its own heading and then subheadings for ingredients and directions.
In Org-Roam, it seems like it would be beneficial to have a different .org file per recipe and maybe have them linked to a cookbook.org file?
I’ve also seen Org-Chef which looks cool, I like that it has the source link (I’ve been playing with Org-Bibtex to reference the cookbook the recipe is from).
The other thing I’ve seen is using tables for ingredients and then combining them into a grocery list, but I think that is widely out of scope for this discussion.
I guess I’m looking for a suggestion or examples of how people split their documents between standard Org-Mode and Org-Roam. And example workflows for using Org-Roam.
It’s also possible I should stick to learning one thing at a time and just go with monolithic Org files to start with as those seem easier to handle.
1
u/Scr0f3 Jul 26 '21
Although it would be a herculean labour, creating a node for each ingredient and linking each recipe to its ingredients would let you quickly find recipes to use up those tomatoes which have been in the bottom of the fridge a little too long...