| I use LogSeq as the general tool, and I started with a combination of PARA and GTD and have tweaked from there. What that looks like is that I use LogSeq's daily journals and extensive use of tags and properties. So maybe that looks like (simplified example): (for list organization) LATER #towatch “20 Days in Mariupol” #documentary - Sandra's recommendation
category:: film Then, I might have another page with a query like: {{query (and (property :category "film") (todo later now))}} but I can also go to the tag page documentary or towatch and have anything I've tagged there. Now, I don't tend to get too deep into watching lists, and stick mostly to non-fiction. I have a book template and article template that focuses me on key insights, and I just take general notes on what is surprising to me or useful to go back to. I take liberal copies everywhere and clean up later. I don't go back daily, but I find it helps when I want to quickly brush up on something or if I want to refer to it in a way that I can send someone else something.
___ Now, to your 4) most of my lists are more work-focused. Again, I use PARA as my storage basics and I've adjusted as I've went. I blur projects and areas more than Tiago does, and use intermediate documents a lot less. I also use daily journals as a lot of my organization because my temporal memory and search generally lets me remember where to put things, but it does mean I have to get back to people later. The real problem is managing the knowledge base and I just keep everything in daily journal until I need to organize it. LogSeq does generally use markdown and lists, but the more features you use the further away it becomes useful outside LogSeq. If I ever moved away from it, my search would largely be "grep". |