• asap@lemmy.world
      link
      fedilink
      English
      arrow-up
      6
      ·
      2 months ago

      I think for some brains it just doesn’t click. How do you write a long form document? How would you write documentation? How would you write a blog post?

      I tried for a while but I just couldn’t understand the concept of “Everything as an outline.”

        • asap@lemmy.world
          link
          fedilink
          English
          arrow-up
          3
          ·
          edit-2
          2 months ago

          Thank you, that’s what I had suspected, so I’m glad I wasn’t doing anything wrong.

          The way I like to think is through long form writing and personal documentation, so I guess it’s not a good match for me.

          In Obsidian I have a script that lets me know any notes that aren’t linked to anything else, so it means I have everything interlinked.

    • ocassionallyaduck@lemmy.world
      link
      fedilink
      English
      arrow-up
      1
      ·
      2 months ago

      I’ve tried logseq for the last 6 months (no commercial license) at work, but while it’s really good for outlining, it’s lack of a tag function is what feels like a critical weakness to me. I realize structurally it’s different in concept. But making everything into bullets doesn’t always suit the task.

      I would love Logseq for journalling or writing though.

        • ocassionallyaduck@lemmy.world
          link
          fedilink
          English
          arrow-up
          2
          ·
          2 months ago

          Yes, but the syntax and documentation on the queries is obtuse as hell in logseq. Like it is ridiculous how granular you have a to get of you want to return all links within a time period or something. If I need to write SQL to pull notes, I should just use a database, lol.

          The nice thing about tags as a distinct entity is it offers the option you can utilize if you choose. It gives you two buckets you can sort into and connect between. And it does make creating “topic groups” easier than manually linking them all to a tag page in logseq, imo.

          Conversely, I would massively prefer of Logseq abolished support for hashtags entirely if they are functionally identical to wikilinks. Or combine them so the hashtags auto-convert to wikilinks or vice versa. But supporting hashtags in any manner when they are frankly not a “real” feature is more frustrating. Making topic links in Logseq is harder because of this.

          Also, the existence of tag pages themselves is a confusong abberation given the above…

          Logseq is a great tool, but very different in terms of what it is best suited to handle. I think I will revisit it for if I do a lot of writing, but for disparate ideas or notation it is good but could be better.

      • drsilverworm@sh.itjust.works
        link
        fedilink
        English
        arrow-up
        1
        ·
        2 months ago

        Obsidian dev’s original project Dynalist is an outline based notes app that does have tags. She doesn’t update it anymore but I still rely heavily on it as my second brain.

    • Virkkunen@fedia.io
      link
      fedilink
      arrow-up
      1
      ·
      2 months ago

      It doesn’t matter if it’s a “far more organised approach”, logseq simply doesn’t fit many types of workflows for note taking.

      logseq is a zettelkasten program; Obsidian is a text editor

        • priapus@sh.itjust.works
          link
          fedilink
          English
          arrow-up
          1
          ·
          2 months ago

          I prefer PARA, which I implement some ideas of Zettelkasten into. Logseq sadly couldn’t do this well. It also just sadly lacks a lot of plugins and features I need/really want. Logseq is great, but so is Obsidian.