Member-only story
[Wonkish]: Refining A New Taskidian for Obsidian
A deep dive into my evolving task management — ‘work processing’ — in Obsidian.
I’ve been revamping an approach to task management in Obsidian that I call Taskidian. This is a long and deeply wonkish dive into the second version of Taskidian: New Taskidian.
In an earlier post — ‘Kanbanibalization’ in Obsidian — I laid out the basics of using the Kanban plugin which underlies New Taskidian. In this post, I want to zoom into some specifics of the technique as I have simplified some of its complexities over the past month or so, in particular cleaning up various remnants of Old Taskidian.
This post relies a great deal on knowledge of Obsidian features and functionality, in particular, Dataview and Kanban plugins, and Obsidian’s model of block addresses and transclusion. If you are uncertain about those, I recommend reading up on them before reading this post.
Kanban and Obsidian
Kanban is a well-known approach to structure tasks in one or more lists, which are (generally) displayed as columnar lists, where the lists represent different phases of a project or tasks assigned to different project members. This was derived from ‘cards’ being pinned to a corkboard, or post-it notes attached to a whiteboard.
