Peter Stuifzand

An easy method I learned for first time users to start using Logseq for real

I often see people searching for the perfect structure or method to use a tool like Logseq. You don’t need that. You only need a simple structure and the will and habit to fill daily notes pages. Logseq does not need much structure to become useful. And when you use it more, it becomes even more useful.

The daily note page makes Logseq powerful without the need for much structure. The following example shows a daily note page. I added a few lines to show how it could look.

- #tasks
  - NOW Finish article about Logseq
- #log
  - 11:22 The article about Logseq takes some time, but it's coming along.
  - 11:24 Logseq whiteboards look interesting.
- #meetings
  - 09:00-09:15 [[Daily Scrum]]
    - NOW Look at issue [[PROJ-342]] with [[John]]
  - 10:00-10:30 [[Coaching/John]]
    - NOW Talk to [[John]] about [[Feature X]]
  - 16:00-17:00 [[Retrospective]]
    - I have some points to talk about during the retrospective. 
- #notes
  - For [[Feature X]] we should take a look at this library.

You can copy and paste it directly into Logseq to see how this looks.

Every day a new journal page is created for you automatically. The page for today is the first page you will see when you open Logseq. Normally this page is empty, but there are a few ways to fill these pages. We’ll get back to this later.

Just before a meeting you can “Zoom in” on the block by clicking the bullet next to the block.

When you do, you see a page, specifically for that meeting. Any notes you take here, show up below that meeting block. After the meeting, you can organize and clarify the blocks. You can add a few tags or additional information that you did not have time to add during the meeting. Now you zoom out and you will see the whole page again.

The daily note page is the place where you add notes during the day. Newer versions of Logseq have an option to quickly capture links from your browser. There are browser extensions for Firefox and Chrome that provide this functionality.

Two plugins can help to add notes to the right blocks. You can use the Quick Capture plugin for notes and the Quick TODO plugin for tasks. Both plugins have the option to add blocks below a parent block. Here the blocks are #notes and #tasks. The right parent block can be configured in the plugin settings.

When you have multiple daily notes with the same tags and you click one of these tags, then on that page you can see an overview of different days with that same tag. It could look like this:

As you can see the meetings from different days are gathered in the linked references section of the meetings page.

On the right of the Linked References title, there is a small funnel icon. When you click this icon you can filter even deeper into the blocks. For example, when you have blocks like these you can filter on the day, “Daily Scrum”, “Coaching”, “Coaching/John”, “Retrospective” and on links that you used in the notes.

With this method, you can filter exactly what you want to see. Click to include blocks with that reference. You could filter for John, or Feature X depending on what you need to see at this moment.

The tags are gathered from all the blocks. There is a special feature that helps to tag the child blocks. When a parent block has a tag, then the current block also has that tag. So when you create a structure with multiple tags, this will automatically tag the children as well.

When you have found the sections that you want, you can perhaps start to think about making this a template. Don’t start with a template, but let it help you when are more invested in a structure.


I think this is a simple structure for when you want to start using Logseq. I have been using this for a few months now and it feels like the right balance between ease of use and structure.

If you want to customize this structure you can tailor the tagged sections to your needs. People use tags for projects, people, topics, questions, or anything else.

The best tip I have for starting with Logseq is that you should not make it difficult. You can always add more stuff. But by starting with a simple structure like this, you can get a good feeling about where to start.

© 2023 Peter Stuifzand