I’ve been using roam research to make a digital garden, a lot of people are interested in this too. I am the first to be using roam and Jekyll, based on my extensive googling and forum searching.
While blogs are oriented around chronological updates, with posts not updated very often. Digital gardens tend to be interconnected, with pages updated regularly.
Roam exports a json blob, not directly usable by Jekyll. So, I have a rake task to turn the blob into markdown pages with proper links between pages.
I store a lot of stuff in roam, and I’d only like to publish a subset of pages from roam, those linked to the page called ‘START HERE’. In python, I a script that parses the markdown and uses networkX to walk the graph of pages, and returns a subset around what I want my blog to be about.
The issue is this so called ‘build process’, requires python, and a ton of dependancies. Redoing the ego graph process in ruby would require some native extensions, which might be a turn off.
I feel like other people would be interested in topic based, roam research backed, digital gardens running Jekyll, so I’m interested in simplifying this process as much as possible, even releasing a plugin for the border community.
Should turning the export into pages be part of the Jekyll build process, or kept as a rake task?
Would having a python dependency (networkX and scipy) be less problematic than requiring a library that builds a native extension?