It seems like this tool is creating a hierarchical document database, it reminds me of XML, but it's json! (or serializes to json at the very least) I don't kn

It seems like this tool is creating a hierarchical document database, it reminds me of XML, but it's json! (or serializes to json at the very least) I don't know what to make of this. I do like the fact that it's a tree, and you can sort of create a document-like hierarchy. The issue with enforced hierarchies is that you now have to find a spot in this arbitrary tree structure for every note you take. It's also a little jarring that list items are treated in the same way that two articles would be. I'm not sure I like that. Lists are a useful readability tool, but articles and chapters are semantic partitioning concepts. I get a little bit of a weird feeling when this is the only representation of the note set that's available. And it feels like cross-referenced notes might be difficult to represent. I do like the representation from a minimap perspective, and it's making me think that maybe the best solution is to use this tree-view as a UI model rather than a canonical representation.