I downloaded Capacities previously, watched some videos, and read some documentation, but I never actually did anything with it. And now I have — created a few documents, which Capacities called “Objects.”

It feels like Capacities is Obsidian 2.0. It does less than Obsidian, but it seems to do all the things I want it to do and perhaps all the things most Obsidian users need. Capacities is not easy to figure out, but Obsidian seems to require programming skills to make the most of it, and Capacities does not require those kinds of skills.

In the past, when I’ve switched to new productivity software, I attempt to build an organizational system early on, but this time my rule is to wait until it’s hard for me to find something or do something, and then add the bare minimum organization to fix that problem. I’ve got a couple of dozen documents in Obsidian now; I’m not going to sit here and attempt to figure out a system that will scale up to hundreds or tens of thousands of documents.

I like Capacities. It seems to do all the things I do in Obsidian, but easier. Like moving from a command line to a GUI. On the downside, it uses a block editor. I do not like a block editor. We’ll see if I can adjust.

Question for those of you who are familiar with both applications: What do I need to know about changing my Obsidian methods and workflows to suit Capacities? I write research reports and articles, each requiring days or months to research and write.