Confusion about the graph view. What's the point of it if you rely on blocks and journals?

General
, ,
2
  • The two workflows are indeed independent.
    • Although they can coexist.
  • If the graph was showing indirect links, it would get too noisy even faster than it already gets.
    • This is not obvious in your example, but it becomes when adding more notes.
    • Should still have the option to do that, but it wouldn’t be practical for big graphs.
    • There could be a smarter (or even full custom) way of choosing when to show links in the Graph view.
      • But currently the Graph view misses many other features.
  • If you want to make the most out of the Graph view in its current implementation:
    • move relevant parts from the journal to the page that they actually belong to:
      • e.g. [[John]] is working in [[Project XYZ]] is knowledge and belongs to page John
        • The rest of the note (i.e. the meeting) is information and belongs to the journal.
        • Page Carla is not related to the other two as strongly as the two are related to each-other.
          • Unless some other note establishes a stronger relation.
      • It is fine to initially write some knowledge in the journal.
        • Moving knowledge to the page it belongs to can take place later, when confident about its destination.
    • read How to leverage Logseq’s linked structure?
      • Some tried and tested advice.
      • Plenty of links to further discussion on workflows.
3 Likes