1/ I am super happy to announce that the “Obsidian42 - Text Transporter” plugin was released to the @obsdmd community plugin list and is available for general download.
Text Transporter is the Swiss Army Knife of text manipulation plugins.
1/ 1st Impressions of the @readwiseio Reader Beta.
I have been testing the Reader Beta for about 2 weeks and I have to say I am super satisfied. It is just a beta, but has already entered deep into my psyche & something I see myself using for years to come.
1/ Over last 2 weeks been playing with @craftdocsapp while working on my newest @obsdmd plugin. For all you #roamans, it is Roam42 workBench, but tailored to Obsidian. I am calling it Text Transporter (for you Star Trek fans) since there is already a plugin with workbench name.
2/ anyhow @craftdocsapp is beautiful. For those looking for excellent block centric authoring with export MD support, this is amazing.
Some of my #roaman friends (@beauhaan) preach the gospel of Blocks. And I agree, blocks are the best unit for work. Craft supports them natively
3/ While Craft is amazing, I still can't see it's future. It is a little between Roam and Obsidian, but not a totally fair comparison. It is simpler and easier to learn. Uses more standard UX metaphors, which makes it a snap to learn.
2/ The word "Complex" sounds negative, but is not.
TfT tools enable new possibilities, but they require effort and commitment.
Is is not just about learning new software & features, but learning new things about ourselves.
We are the tool of thought, software is the helper.
3/ TfT tools are complex because we have to make changes to ourselves - the way we think, process & use knowledge. We have to be willing to invest time, energy & in some cases money to learn new techniques, processes & workflows.
In 1980, @TheTedNelson in one of his books coined the phrase transclusion and even demonstrated it in his own Xanadu Project. Transclusion says you have a single document assembled dynamically from separate sources.
3/ It is good to educate yourself on the transclusion as it helps you better understand the goal of block refs. I suggest this Wikipedia article. It’s not a new idea, the concept of compound documents have been around for a long time.
The Opinionated Short Guide for Switching from Roam to Obsidian
1/ Many have asked for advice on making the switch. While there is no "one size fits all" approach, I will share some practical tips that should help you.
Other switchers - feel free to hop in with your advice
2/ -- Give yourself time --
Over time, we build complex workflows & techniques in a Tool for Thought like Roam. There is no button to instantly transfer you to a new tool. You need to give yourself time to make the transition. Some say 2 to 3 weeks, I gave myself 2 to 3 months.
3/ -- Export from Roam using Flat Markdown --
Export your Roam graph to flat markdown files using the export tool in the menu. This will give you a zip with all your pages in Roam, in markdown format and with all block refs resolved to pure text.
1/ I submitted my 1st plugin to Obsidian for review. The process is nice. Not only is the dev experience good & support via the forums helpful, but the process of submitting a plugin makes you feel confident in @obsdmd leadership.
Here is the feedback I got with needed fixes
2/ You develop your plugin and then you submit it to review. Obsidian tests the plugin and then does a code review. The review is looking for a number of things that will improve the quality, reliability and secure usage of the plugin.
3/ First they make sure you are consistent with their User Interface features. This makes sure the user experience is standardized.