I usually have various projects on the go at any given time - mostly either code or articles. To manage the workflows for them, I use kanban boards. I have two main ones: projects and writing.
Because I’m a heavy Neovim user and I like to keep my things plain-text so they’re easy to backup, I use a file system based approach for organizing my kanbans which I describe here, and which I operationalize using my plainban project. For example, my writing kanban looks like:
01 Icebox
-- abcd-article-a.md
-- def1-article-b.md
02 Prioritized
03 Draft
04 Edit
05 Ready for distribution
06 Distribution
07 Done
-- cool-article-a.md
-- lame-article-b.md
08 Cancelled
09 On hold
I’ve recently moved to using JD to organize most of my notes. At the moment I have a layout which looks like:
10-19 Creative
----- 11 Projects
-------- 11.17 Writing Kanban
20-29 Admin
----- 25 Money
And then, within 11.17 I nest the structure above. This seems like an okay solution, but I don’t love it because each item within the kanban could plausibly live somewhere completely different in the JD hierarchy. I.e. an article like ‘using beancount for fun and profit’ which is in draft could live either in 11.17 Writing Kanban / 03 Draft or somewhere in 25 Money.
Wondering if anyone has ideas on how to synthesize these systems, or even if they’re possible to synthesize? The system extension / breaking the rules articles are suggestive, but I’m not quite there yet.
Edit: Realized that on UNIX operating systems this can probably be overcome through use of either symlinks or hard links; you would link from a kanban ticket to the desired final file location and work by moving links between directories in the kanban. But doing this does seem to violate at least the spirit of JD.