With different types of tasks, I could search based on when and how they need to be done. When doing focused work, I can narrow it down to - [ ]. When following-up with different members of my team, - [@]. Looking for tasks that were on the back burner, but now I have time? - [>]. etc.
I understand this would probably cause issues for the progress bar, but for my purposes at least, anything other than - [ ] would count as “done”.
Would love to find someone with the skill to implement this, but also open to work-around ideas. Thanks!
This sounds pretty interesting and I could see myself using similar in my workflows.
I don’t think I have the skills to implement it but I’m curious if this is something you know is a feature in other pieces of software with check-boxes. If so do you have an example of what does it look like to use from the user’s point of view? Handling the markdown and code is all good but having some UI to support it in the rendered view would probably also be a good idea.
Hi @craftzdog! I’m starting to make this plugin. I’m not so familiar with Remark, so I need your help because I have some questions.
If I understand correctly, first I need to make like a plugin for remark to recognize other checkboxes as real checkboxes, like a regex to capture everything that is like - [ ], let’s say - [-], - [<], etc.
Then I need to push that plugin into remark and to create my own <input type="checkbox" /> component which I will be adding different styles to render on the preview.
Sounds right to you? Could you point me to other plugins or resources that did something similar not to start from scratch?
Great to know you are trying to support them.
Yes, you are right.
Currently, Inkdrop uses the older version of Remark and I’m planning to upgrade it to the latest (Micromark) in the future (maybe this year).
It will involve many breaking changes, so I want you to wait until then.
Remark (Micromark) is an AST-based processor.
There are so many plugins available so you can check them out to learn how to build it: