Interesting point. Are you thinking about this from the parser/tooling side, or from the person writing and reviewing the file?
We intentionally started from Markdown because we wanted .void files to stay standards-compliant and not reinvent a new document format. Markdown already gives us a familiar, portable way to write docs, notes, examples, and explanations around the request.
Frontmatter handles the document-level metadata, Markdown stays the human-readable documentation layer, and the structured Voiden blocks handle the executable API parts.
We could put everything into one YAML object, but then the file becomes more like a config file than a Markdown document. The tradeoff we’re making is: keep the file readable in GitHub, PRs, and plain text editors while it still gives Voiden enough structure to execute requests reliably.
But then how did Postman became so popular - we can't deny it became the default.
subscription based right?
A list I made btw - mostly on markdown :
https://github.com/dp1620/awesome-markdown-devtools
But whyyyy?
But how do you collaborate?
so proton is now a movement.
Hehe - those were the days my friend - we thought they would never end - we sing and dance forever ----
lol
all the comments are written by humans and no bots.
I guess the need is going to only increase !
Just in case you wanna try it out : https://voiden.md/
We have a very different approach to API tooling.
Awesome - would love some feedback !
Just fyi - voiden too is not us based.
Happy to help out - Check out our docs too - https://docs.voiden.md/docs/getting-started-section/intro.
Its trigonometry - big brain time.
They never learn.
:)
Interesting point. Are you thinking about this from the parser/tooling side, or from the person writing and reviewing the file?
We intentionally started from Markdown because we wanted .void files to stay standards-compliant and not reinvent a new document format. Markdown already gives us a familiar, portable way to write docs, notes, examples, and explanations around the request.
Frontmatter handles the document-level metadata, Markdown stays the human-readable documentation layer, and the structured Voiden blocks handle the executable API parts.
We could put everything into one YAML object, but then the file becomes more like a config file than a Markdown document. The tradeoff we’re making is: keep the file readable in GitHub, PRs, and plain text editors while it still gives Voiden enough structure to execute requests reliably.
That's a great observation !
It right now helps in opening a specified file or directory in Voiden, see the version, etc.
You can check out more in the docs here : https://docs.voiden.md/docs/developer-tools/voiden-cli