I’ve been using Logseq for quite a while now and love it, however I’m kind of stuck on something in my process. When I work on something at my job, I’m often working on it for multiple days. How does anyone here capture that?

Do you do something like this?

[[figure out how to create x]]  
  - item 1  
    - subitem 1  
    - subitem 2  
  - item 2  
[[change out every y in all of the zs]]  
  - action 1  
  - action 2

The thing is, I can then go to each one of those as a page and see everything, but I can’t add to it for that day. I can just start the next day with an entry of [[figure out how to create x]], but I won’t be able to see the whole thing while I’m doing it. I also won’t be able to add something in context, like this without removing it from the day I’m working on it:

[[figure out how to create x]]  
  - item 1  
    - subitem 1  
      - subsubitem 1  
    - subitem 2  
  - item 2

I see that you can copy and paste block refs, but that largely is the same thing as a page.

Do any of you deal with this? Should I not be so concerned about keeping my edits for the day?

  • appropriateghost@lemmy.ml
    2·
    3 days ago

    If these are just random ideas to brainstorm for a project, you could just assign a unique hashtag… like #2025project1

    Then you can view that specific page and see all the references. The page is created and you can start working permanent notes to that page or continue using journal mode to collect ideas.

    I don’t think I will have much success trying to work on a project in journal mode, so permanent pages are important, but the journal mode lets you collect ideas so you can later organize and make official in its dedicated page.

    • Ken Oh@feddit.onlineOPEnglish
      2·
      2 days ago

      Yeah, I think I just need to de-couple the idea of a journal with some multi-day task or project. Good idea. I do think I’ll keep the journal thing since my job has a lot of physical equipment in/out that I like to just mark down.

      • appropriateghost@lemmy.ml
        3·
        2 days ago

        that’s good. I love Logseq for the simple reason that I could have a quick idea or resource or text that I need to save but I don’t want to sort through having to put it in a proper place. By noting an idea in journal mode and using the appropriate hashtags I can then go to the proper project page and later see what needs to get done. Especially useful for TODOs which will show up in the referenced section of the appropriate hashtag.

        I really like the logseq workflow. It has its purpose of just dumping information that allows me to recall it later and not have to spend time and energy saving these in random files. I also especially like that it doesn’t mess around with the folder structure. If I for whatever reason decide to stop using logseq, the assets are in place, the journals are in place. It all just works well. It’s one of my favorite things that I’ve discovered in a while!

      • Bas (Tools on Tech)@pkm.social
        3·
        2 days ago

        @KenOh @appropriateghost Journal is mostly to collect things and pages are references. I usually make a page per project with a main task in it tagged with project. That way I can easily find my open projects. Put that in the sidebar and while journalling know what to link to for time records/meetings.

  • INeedMana@piefed.zipEnglish
    2·
    3 days ago

    I’m not sure I exactly grasp what you mean. But if I do, I’d do it like this

    Create file projects/x/item1/subitem1/subsubitem1
    Inside add a header on top with a ref to date of work

    # [[2025/07/03]]  
* that way when you open the file, you see the most recent note  

# [[2025/07/02]]  
* bar  

# [[2025/07/01]]  
* foo

    That way, using hierarchy and references parts of 2025/07 or projects/x you can see what you were working on in that month or how did the whole flow for an item go

    Does that address your issue?