Roam is like a good swiss army knife, it even has a ClojureScript development environment. I spent the past 14 days getting acquainted with {{roam/render}} . This post serves as a note-to-self, to summarize and organize what I have learned.  This post is targeted at developers and Roam hackers. If you are not in one of these camps, you will likely struggle with the content.

Which are the longest paragraphs in your graph? Which pages did you edit or create last week? How many paragraphs of text do you have in your database in total? Which pages do you have under a given namesapece (e.g. meetings/)?

I have perfected the process of importing ePub books into Roam. I was able to create an almost frictionless experience for reading a book in Roam. Put aside the issue with reading on a tablet screen instead of a kindle, this solution is much more comfortable and efficient for reading and note taking at the same time then the Kindle. I have also develop a solution to automatically maintain full traceability from my notes to the source text even though the ePub book sits in a different Roam graph compared to my literature notes. This post is a detailed how-to guide for setting yourself up to read books in Roam. Here is the link to the Python program you need for converting your ePub books: Colab Notebook Here is the link to the Book-base.json that will be required to achieve the full experience. This is how the end result looks Detailed how-to walkthrough This second video explains the full process from the beginning to the end in 27 minu...