Best Practices for Structuring Notes in Logseq for Long-Term Projects

Questions & Help
1

Hi everyone… :wave:

I have been experimenting with it for the past couple of weeks. I love the flexibility and the ability to link thoughts together seamlessly, but I’m having some trouble figuring out the best way to structure notes for long-term projects.

I’m working on a couple of big projects that might stretch over several months (or even a year). The projects involve research, daily task tracking, and the accumulation of a lot of different types of information—both big picture ideas and smaller details. I’ve been using Logseq daily, and while I appreciate the daily journal feature, I sometimes feel like it becomes hard to trace the overall progress of these long-term projects without digging through daily logs.

What I’m currently struggling with is:

  1. How do you organize long-term projects in Logseq? Do you use specific pages for each project, and if so, how do you balance those with the daily journal entries?
  2. How do you keep track of progress or major milestones? I’m finding it tricky to get an overview without getting lost in a sea of notes and links.
  3. For research-heavy projects, what’s the best way to organize and retrieve sources or reference materials? Right now, I’m just linking them in various places, but I’m not sure that’s the most efficient method.

I also check this: https://discuss.logseq.com/t/note-taking-and-linking-ideas-in-trilium-and-logseq-your-ideasservicenow But I have not found any solution. Could anyone guide me about this?

Thanks in advance!

Respected community member! :blush:

1 Like
2

Welcome. My personal answers to your points of struggling:

  1. Read Data Entry in Journal or Pages?
    • Follow the links for more detailed advice.
      • For example:
  2. Should be done through queries.
    • That implies that the progress-relevant notes contain tags and/or properties that queries can work with.
  3. Consistent linking should be efficient enough, as long as the previous two points are respected.
3

Block of Blocks (you can call that a Page or not, conceptually speaking) is what I use for Projects, Areas of Responsibility and other long-term or not-short action-oriented information containers.

You build inside that whatever retrieval layer you might need that brings you back information spread out throughout the whole graph over time.