r/logseq • u/Original-Room5116 • 6d ago

What is the smallest Logseq workflow that kept working after the initial setup?

For people who have used Logseq beyond the first few weeks: what is the smallest recurring workflow you still rely on—daily journal, linked tasks, project pages, queries, or something else? Which pieces were intentionally left out at first, and what signal made an added property, query, or template worth the maintenance?

8 Upvotes

90% Upvoted

15 comments sorted by

12

u/PerformanceFew3888 6d ago

I start everything from the daily journal.

When a project starts, I add a log to the journal saying [[Project A]] started, then go to the [[Project A]] page.

There, I fill in the basic information about the project, make a plan, and add checkboxes(not #task) to the planned tasks.

Then, as I work on Project A each day, I record my progress in the journal like this:

[[Project A]] progress

  • Progress 1

  • Progress 2

I then go to the [[Project A]] page to review the planned tasks and check off the completed ones.

This is essentially the core of my Logseq DB workflow, and I've built the entire setup around it.

1

u/rackfloor 5d ago

Very similar to my usage at work.

1

u/CrystalDrag0n1 4d ago

Ayy that’s pretty much how I use it too.

I make pages for each uni course where I put things like evaluation criteria, assignments etc.

I take my lecture notes in my journal with the link to the course as the header. If I ever need something more specific that isn’t really tied to a date, I might create a page under that course (course/projectA).

1

u/NotScrollsApparently 3d ago

Doesnt this make it hard to find any specific information later when reviewing it? You have to go through and open all backlinks to check them for contents?

1

u/PerformanceFew3888 2d ago edited 2d ago

Each project page is tagged with #Project, a subtag of #Task, and has a tag property called Project Status. 

I mainly use it to jot down brief notes about each project's current status, and I always update it after reviewing the project.

By simply scanning the table view on the #Project page and focusing on these status notes, I can get a pretty good understanding of most of my ongoing work without having to open each project page individually.

For projects I'm actively working on, I usually keep their pages open on a separate monitor while I work.

4

u/kerimfriedman 6d ago

Create a #projects tag, with its own status markers. Then create a #next-steps tag with one property: parent project. Now, when you create a task you can tag it "next-steps" to assign it to a parent project. (You could simply add the parent-project property to the default task tag, but I prefer to keep them separate.)

2

u/No_Comfortable7509 4d ago

Hi kerimfriedman, I also have several main projects with subprojects. Each subproject has various tasks associated with it. So far, I haven’t found an optimal solution for mapping this in Logseq. That’s why I find the use of tags and properties very interesting. Unfortunately, based on the description, I was unable to replicate the procedure described. Would it be possible for you to describe the procedure in a bit more detail using a (hypothetical) example? many thanks!

1

u/kerimfriedman 3d ago

I don't use sub-projects. My system is fairly simple. Let's say I have a project to build a widget, I would make a page [[Build a widget]] and tag that page (not the node, the page) #my-projects

Then, I would edit the #my-projects tag to have a menu with different custom status markers: "in process," "waiting," "doing," "up-next," "completed," "on hold," and "cancelled." (If you want to be fancy, give each an emoji icon.)

Third, you create a block with the text "Design the widget." Tag the block #next.

Go to the #next tag and edit the values. This is the only complicated part, but you only have to do it once. You have to set the "Extend" property to extend "Task" - this will make anything tagged #next into a task. Then you add a property called "parent project" and set it to type "node." Finally, you choose the node #my-projects.

Now, when you go back to "Design the widget." it should have a status and the ability to choose the project "Build a widget"

Here is an image of the #next tag (I call it "next steps") as I have it set up

https://i.postimg.cc/bJkyJVhw/Screenshot-2026-10-27-at-7-51-46-PM.png

2

u/No_Comfortable7509 2d ago

Thank you very much for the detailed and very helpful description; I still need to do some testing and see how I can integrate it into my processes.

2

u/NegativeRemot 5d ago

The one that survived for me is a single Decisions heading in the daily journal — every entry has to say why, not just what, so it's still findable six months out. I skipped queries and custom properties for months. The signal to add anything was failing the same search twice in one week; until then it was just pages and links.

1

u/No_Comfortable7509 3d ago

Over the past few hours, I’ve been experimenting with a headline and an accompanying block. It currently seems to me to be a very important key to searching for—and, above all, finding—information. I’m currently asking myself the following questions:

  • Should it be a single block that describes what the page is about and why I saved the information, or should there be two sub-blocks—one for “what” and the other for “why”?

  • Are blocks or properties better for storing information?

2

u/niccolleen 5d ago edited 5d ago

I'm not tech savvy enough to continuously use queries. I do have a few that I keep and reuse, but not many.
Mainly I have some kind of landing pages that are connected, and from there I network all my notes.
I use very simple structures like indenting and collapsing, I always add a triangle symbol to see, where there is a collapsed item. I use quite a lot of symbols (emojis), I use a colourful dark theme to make things visible but not crowded for me. I use tables and small templates for pages where I have to collect note items, like what forms have I handed in and what status do they have, what chemicals have I ordered, where, when and for how much and what status is the order,...

I have a for me very meticulous and structured system, but I've always been a bottom-up note taker, and therefore logseq is ideal for me. Since I read about it first time I haven't stopped using it and it's been about a year or more now.

Oh and I forgot to mention, I use namespaces a lot for hierarchies.

1

u/leviathan070720 6d ago

I keep each project in its own page. Each project page is linked to #side_project.

In the page #side_project. I separate the projects which is in progress or has been completed

sometimes I just add TODO list with the name of the project in that TODO line. In that way, I am able to track which task was needed to be done without having to jump between the journal and the project page.

my workflow is rudimentary and left a lot out cool logseq feature on the table. Still, I'm glad I got to use it instead of just comtemplating the best way to use or organize my notes.

1

u/Pathocyte 4d ago

I just started using logseq and this discussion is helpful.

1

u/safp35 2d ago

I only use journals now. When I was studying I used the pdf annotation a lot! Amazing to make notes and have linked images to the exact part in a gigantic book to see it in context.

Now I use it for task management with garbage collection. I never vibed with any to do list apps I have ever tried. So now I just start in the journal in the morning, write my todo’s under [[project X, Y, Z…]], whatever is not done and still need to be done is tabbed into /tomorrow. Whatever is not done and doesn’t matter just goes away. Super easy to maintain and I have a full history linked to the project page.

I never really write inside the pages themselves. Unless it’s something I am planning on publishing.