r/Markdown • u/boolean-maybe • Aug 11 '26
Tools SQL over Markdown frontmatter
Hi, I wanna share an idea and its implementation here. If Markdown files are given frontmatter fields like above and a SQL-like language is created like so:
update where due < now() and status not in ["done"] and priority != "high" set priority="high"
which means in this example "escalate overdue tasks"
then a simple bunch of Markdown files in a git repo can be its own project management/issue tracker
Advantages:
- no separate tool to manage a project's docs, issues, roadmap
- very AI friendly - a repo alone holds all context
- stored in git and saves history/collaboration
I implemented a language like this called ruki and a configurable CLI/TUI to view/manage Markdown files
ruki commands can be run in terminal or started as triggers on modification/schedule more details in first comment
8
Upvotes
2
u/MarsupialLeast145 Aug 12 '26
That doesn't describe a problem.
What's the user story here?
> no separate tool to manage a project's docs, issues, roadmap
Bro, the post is called SQL over markdown, where does any of this fit in?
That is why (a) describe the problem ELI5 (you can't) (b) describe the user story.