

Both graduated from Stanford, Jesse in 2003 with a BS in Product Design and Mechanical Eng.
#Workflowy link to node software#
Workflowy was started in 2010 by Jesse Patel who seems to be there still 13 years later and Michael (Mike) Turitzin who sold most of his part and is now a Software Engineer at Figma. I highly recommend watching that video, not now, after you read this! :) Back then the app was called Work Flowy and somehow was renamed to Work flowy, so less emphasis on flow? I kid! Looking back at my old emails, the first time I heard of it was in Scott Hansleman's 2012 talk " It's not what you read, it's what you ignore". This week's app is Worflowy which my sister Janet started using back in 2016 mostly for work but then also with her family and our families. So I just create a new ZK note and write in there, referencing whatever I want to reference (including today’s daily note!) and I know it will show up in my search results or backlinks when I need it.Welcome Ricardo from no-fixed address, Esther from New York, Reginald from Florida and Captain Nemo (!) from Italy. Honestly I don’t even care what the name is, but going with “untitled 1, 2, 3, etc.” just feels wrong. I just want it to show up in search results / backlinks when I need it. Maybe I could break this up into atomic notes, but really there’s no overarching idea from this that I want to show up in my page name autocomplete. This is where the Zettelkasten prefixer core plugin comes in! I want referencing a page name to be meaningful, with something like an evergreen note title or a keyword. I may want to reference the contents of those pages, but unlikely the titles.

“What I’m thinking about with GuidedTrack on ”.I’m unlikely to reference any of these page titles, so having to title them is unhelpful for me: One of the problems with this approach, however, is that if you use the double brackets as a form of autocomplete, then you end up with really noisy results there! This is because you create so many pages that each have their own name that if I’m just trying to pull up a specific page I have to sift through a lot of crap. In Roam, my Daily notes page would look like this:
#Workflowy link to node how to#
I’m also in a group of other Roam expats trying to figure out how to make Obsidian work for us. For context, one of my side projects right now is working on Figma plugins to make it better for knowledge management purposes. Here I have an example of the daily notes in Obsidian and Roam.

But in Obsidian, you need to get comfortable with many separate pages that each link to everything you want, and you also need to get comfortable with navigating a few steps - finding a page and then clicking on the atomic pages that it links to, rather than expecting to find everything in your first query. These pages won’t necessarily be as atomic or contextualized as having many branches of a tree in Roam would. So in Obsidian, you make a lot of separate pages, and make sure those pages have all of the information you want available in a search result or backlink search on those pages.
#Workflowy link to node full#
I have a description below of what’s essential to this post, but you can see a full writeup of the way indentation trees work in my winning roamgames onboarding submission I really think that’s probably the biggest thing Roam expats need to get used to… Roam interprets branches of trees (in filters and queries) in the same way that Obsidian interprets a page (in search and backlinks).

Below is a description of both, and how I’m adjusting to better utilize Obsidian’s strengths while gaining a similar effect to Roam’s approach. I learned quickly that the design of Obsidian does not support my old “throw everything in the daily notes” approach from Roam. I’m not fully convinced yet, but very optimistic. I’ve been using Obsidian for a while and loving it to manage the markdown files on my Jekyll based website, but I’m trying to see if I can really work in Obsidian. For the past few weeks and over the next month or so, I’m attempting to transition my work from Roam to Obsidian (mainly due to slow performance when I push it with queries/backlinks).
