I have experimented with those “smaller” tasks. Their main appeal is that I can write them anywhere. In a middle of a note, another today note and so forth, and they could all be collected and shown in central location. In daily note, or in the sidebar. My system too has a central location (daily note), but the process would be a bit more “heavy”. I do have a template that can be called for creating new notes and that takes away some of the friction.
I have a tag #tasks inline in my task-notes (still thinking about using YAML), and I’m primarily calling that when I do the dataview-query. I then have a bunch of fields in the daily note (Project, Deadline. I don’t list the DoDate there, as the table is showing tasks that are Due that day, so it’s redundant). I don’t worry that much about having a checkbox there, as I would have a link I could use to go to the tasks note.
Yes, my task-files all look the same, see earlier the contents of the note.
Thanks to your help, I have pretty much gotten this to work. There is still the issue of working with dates that are not today. For example, for todays tasks, I have this dataview query:
TABLE Project, Deadline
WHERE date(DoDate) = this.file.day AND completed !=1
And for tomorrows tasks I have this:
table Name, Project
where date(DoDate) = date(tomorrow) AND completed !=1
Both of those work perfectly when looking at todays (18th) note. But if I look at tomorrows (19th) note today for example, it will show me tasks means for 19th in the first table, and for tomorrows tasks it lists the tasks meant for 19th again, because I’m looking at the note on 18th, and right now 19th is “tomorrow”. “Tomorrow” should be in relation to the actual note, and not to the date when I happen to be looking at it. But I have a feeling that fixing that would be very complicated so I might just live with it :).