Technology

Well I think the first thing is just simply that documents aren’t notes, so you wouldn’t write those things in Logseq.

What you are writing in Logseq is a zettlekasten, which is just a personal knowledge graph. And in a knowledge graph, everything needs to relate somehow to everything else, that’s why it has to be an outline.

So things can relate to the journal date they were written on, to their parent and children concepts, and to the links that they contain. Every idea has at least a relationship to the date you wrote it, but hopefully you can link that idea to more than just that relationship. You want to organically rediscover that next time you make a cake, that eggs are bad for your allergies, and be able to trace that you discovered that at this doctors appointment on this date.

Otherwise, how would you ever find anything? And more importantly, how would you rediscover it organically when researching other concepts in your graph?

Obsidian purports to help you create organized knowledge graphs, but it makes you plan your organization up front. Logseq lets it evolve naturally and organically, by giving you the necessary tools and constraints.