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.

This post summarizes my learnings from the Roam Agile project. I present the Minimum Viable Product (MVP) version of the Agile Development Template. Here you will find the link to the Roam EDN archive containing the template, instructions for how you can get started, YouTube videos showcasing the solution, and a link to the graph I used for my project with my backlog, user stories, sprints, daily standups, customer feedback, etc.

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/)?

This is a quick walkthrough of two powerful approaches you can take to debug your JavaScript code in your Smart Blocks in Roam.

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...

In this post I will present my final solution for getting the Bible imported into Roam Research . I have finally found a way to drastically decrease the size of the imported Roam graph, but still have a reasonable solution for accessing multiple translations and cross references. I will share my thoughts on performance and potential next steps for making the Bible work even better in Roam. If you are interested in the topic, I have two other posts on the subject. Links are at the end. You can download the Roam .EDN archive for the Bible from here: ASV.edn For a real time demonstration of the full import process within 3 minutes check out this video . WARNING: by restoring the ASV.edn into your graph, all other data in your graph will be lost! The source code for the converter is here:  Roam.json Bible importer with BUTTON for verse numbers v1.ipynb Use this if the primary translation you'd like to use in Roam is ...

This post is a bit more technical in nature, though I think the first half may be interesting even to those who are not into Python and the inner workings of Roam data import. What is Roam? Roam is a bit like a personal Wiki. It is a note-taking application that supports networked thought. At its core, Roam is extremely simple to understand. A Roam database simply consists of pages and paragraphs. The paragraphs are displayed as bullet point lists which can be nested much like in an outliner. In Roam lingo paragraphs are called "blocks" When writing, you can simply reference other pages using double square brackets. For example to reference my page in Roam for Zsolt's Blog I just write [[Zsolt's Blog]]. Now if I click on the reference between the brackets, Roam will take me to the other page. What makes Roam unique is how you can reference not only pages, but also blocks by entering the block's unique identifier in ((round bracket...