Meeting and discussion notes vs Knowledge Base

Questions & Help
1

Brand new to Logseq, so I’m wanting to get off on the right foot.

I would like to track two main areas of notes. One would be notes related to projects, meetings, and discussions. The other area of notes would be a knowledge base of code snippets and more technical IT related information. As the amount of information grows, I’m wondering if creating 2 separate graphs would be advisable to help more quickly drill down when retrieving information. Or if keeping everything in one graph and maybe having some key pages favorited as starting points depending on the type of information being seached for?

Thanks for any ideas.

1 Like
2

Welcome.

  • Having a single graph is generally more convenient.
    • Retrieving information should not be a problem.
  • However, merging graphs without connections between them is not advisable.
    • After some unspecified size, performance starts suffering.
  • The question is whether there is any cohesion between the two graphs.
    • Try thinking of a graph as a single project.
      • If you can easily imagine yours as two separate projects, they should probably be two separate graphs.
2 Likes