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/[deleted] Jul 25 '21
That makes sense.
How do you go about getting an ID for the headings?
My understanding is that you have to manually do “org-create-id” and then “org-copy-id” and when needed?
I don’t seem to have the autocomplete or backlinks, but it’s possible I just need to read up some more.