I’ve migrated from obsidian to logseq and I’d like to mention that at first I was feeling very weird out by the bullet points but after seeing my spouse using it, it kind of clicked for me.

I’d start by creating an “Index” and linking the thing you want to write about there. You can then decide if you want to write it as bullet points or like checkboxes using TODO at rhe beginning.

There’s no right way of taking notes, attempting to find the ideal way will just prevent you from writing them. Put the information down and then you can organize it through moving the blocks around and such.

I’m a logseq user of about 6 months and overall really like it. It’s mostly built around the daily journal, which mostly works if you lean into it. I basically write what I did, todo’s or random thoughts for the day in there. I typically segregate my root bullet points into a handful of main “buckets” like a job, client or project. I used to do those with a hashtag like #job1 but moved to page tags like [[job1]] with sub bullets for main tasks, todos, notes, etc from each. i have many relevant hashtags for relevant subsystems/topics relating to the main ones.

from there I have setup some basic pages for things like [[job1]] with a query to show TODOs with that task (see below), then some relevant reference notes, and sometimes some links to bullets from previous journals if i find i will likely reference them frequently. you also can see below the linked references, which is frequently useful. i also frequently put tags to other tags, pages, etc. within to help map everything together

here’s an example of a very basic query I would keep at the top of the [[job1]] page {{query (and [[job1]] (task NOW LATER DOING IN-PROGRESS TODO WAIT WAITING))[[job1]]}}

to your above, you have #workimprovements, you can either just jot those at the root as they come to you and include the full hashtag, or you could have a starting section of either [[workimprovements]] with various ideas below, but i would also suggest adding in other relevant hashtags for subtypes, areas, etc. another tip about hashtags, don’t go crazy with them – too many hashtags just makes a mess – but don’t skimp on them either. If you think you’ll use it frequently enough, or at least want to go back and reference it easily in the future, make a hashtag. you can use the hashtag plugin after the fact to find unused and remove hashtags you didn’t end up using.

one thing I really wish they would add is similar to hashtags, but for people. Right now, I “tag” people with an @ in front of their name, so I might have @BobS requested X which sort of helps to go back and search for things related to @BobS, but it’s not natively done for fully fleshed out. It would be awesome if there was either native or a plugin functionality to more gracefully tie it together

anyway, there’s my logseq ramble, hopefully it helps.

Great. Thanks for the suggestions. I have a work project starting up next week that I want to keep track of with logseq. Hopefully I can make some improvements to the way I normally try to keep up with all the stuff that should be done.

I’m a Logseq novice, but I’m happy to help workshop ideas.

If you’re just editing order and organizing thoughts you can reference blocks between pages with ((double parentheses)). Those could be as their own line/bullet, or even in-line with other text. So with that you could make a new page (or block in your daily journal) with new text summarizing your findings and block references to pull the previously taken notes in whatever order works best for you.

If you want the existing notes to be referenced but also cleaned up for presentation you could do that and use block references as mentioned, or you could use an Alias to link to the block while preserving its content. It depends on how you want to cite yourself, so to speak, and if you want to preserve your existing notes word for word.