It hits the sweet spot for me:
- Plain Markdown files stored in git; exactly what I am used to for code.
- Editor is VisualStudioCode, which I always have open, and can configure however I like.
- No vendor lock-in.
I can make pretty much the same argument for say, vim or emacs, and say that plain markdown + fugitive/magit hits the sweet spot.
I am just trying to understand where's the vendor lock-in thing coming into the picture here.
I really don't get why I can't just point to any Git repo for syncing purposes.
Not only that but I can’t see anything to stop you setting it up in a more typical cloud file syncing service (e.g. Dropbox) directory and having everything happen effortlessly in the background?
Maybe you can share a bit about how you organize your written down knowledge?
I use metadata sections in the header of each document to organize and configure it.
The documents themselves are structured differently depending on their topic. My journal document is a long running single document with timestamps. Other documents are structured in paragraphs, others are simply bulleted lists. Of course, everything is linked by tags, which are the core organizational mechanism.
I've found that rigid organizational structures don't lead to better outcomes. It's best to let the structure develop naturally through tagging.