-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Todos in markdown #1
Comments
Hey, is any progress already done? I really want to develop my own todo tools based on markdown but they all seem to diverge. Also, where is the specification in your project? |
@lquenti I reached out to several maintainers of other projects, and there was initial interest, but unfortunately that was as far as it went. I'm personally motivated on this topic, I'm really in favour of hosting data in simple, human readable, future proof formats. But I'm not sure how to create a space where others are also motivated to collaborate. With regards to my own action.tools project, I'm happy to document the format. I'm also open to changing it. I've been using the tool myself for maybe a year now, and I've learned a bit about some of advantages and disadvantages of the format I chose. I started an issue on the documentation topic, happy to discuss in more depth over there. @lquenti How about jumping on a quick call to discuss your goals and see if there's potential to collaborate on formats? I'm reachable via @chmac on Telegram, Twitter, etc, or also via email if that's preferable. |
Yeah, sounds great, I reach out via Telegram. I just saw your For example, every markdown document should follow some basic structure. If an Kanban View is needed, the document should also have a maximum headline depth of 2 etc etc. This would allow that for example |
Another useful project to consider is taskell which does kanban style boards from a markdown document in the console. Would potentially be interesting to build a web based version so these could be viewed on mobile devices... |
There are a few projects storing todos in markdown. This issue is an effort to find a simple format that's acceptable to as many projects as possible, with the hopes of achieving interoperability between projects.
The text was updated successfully, but these errors were encountered: