I’ve been looking into all sorts of them recently: logseq, appflowy, vikunja, etc. What tools do you use? Why? What problems did you run into with the previous set of tools you used for this job?

Right now I’m primarily interested in finding a “zero-knowledge” (cloud provider doesn’t have access to my data) system for task management. Needs to be able to have recurring tasks and tasks organized in some interesting/useful ways (by projects/labels/something, maybe a kanban and table view). Deadlines and time tracking/planning interesting but not required.

  • clothes@lemmy.world
    link
    fedilink
    arrow-up
    2
    ·
    4 months ago

    I keep failing to make Zettelkasten and org-roam work for me. Do you use a single knowledge base for your whole life, with millions of tags and pages? Or should I be making separate directories for each project? Is the “daily journal” the best place to put everything, with well tagged entries?

    You don’t have to answer all of those!

    • Sem@lemmy.ml
      link
      fedilink
      English
      arrow-up
      2
      ·
      4 months ago

      No, I have two different things:

      • org-mode files with schedule, diary, tasks, etc.
      • knowledge base, org-roam (orgnote). I have a single base but it contains graphs about topics and these graphs are not connected

      I like that approach, because I use orgzly-reviwed on Android with a notifications. And because it is simpler to maintain knowledge base.

    • finestnothing@lemmy.world
      link
      fedilink
      arrow-up
      2
      ·
      4 months ago

      Honestly, whatever works for you.

      My preferred system is two big directories, one for your daily notes (dailies, journal, etc), and another for literally everything else.

      This is how logseq is implemented, and can easily setup emacs org-roam to do it too. It’s very nice because you don’t need to worry about where to put something, throw it in your daily journals and get all the info down there, and link densely. If it’s about a specific topic, link to it and when you go to that topic you’ll see the info in the back links below (logseq does it automatically, emacs take a bit of config). You can then transcribe the important/summary/etc info from all of your aggregated back links into a single well thought out and planned document, or at least a single trimmed down one. Or, just leave all the info in the back links, whatever works best for you