

That’s a great observation !


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


No it does have a CLI too and we are planning for a CLI runner very very soon !


I am making a GitHub repository https://github.com/dp1620/awesome-markdown-devtools for markdown tools - I will include revealjs.com along with sli.dev


lemmy is really really cool.


my goodness - I saw this pretty pretty long back.


Thanks - do give us a feedback :)


imo Swagger is good for looking at the API. For local and odd setups for example If you need shell scripts swagger becomes pretty rigid.


You can join our discord to meet people who are using it : https://discord.com/invite/XSYCf7JF4F


caffein rich whey protein.


the best possible answer.
but from a programmers perspective - shouldn’t it feel natural - you just keep filling up forms doing the same work again and again?
It means a lot of API tools feel like form-heavy tables where you just fill fields and hit send.
For example, testing CRUD often becomes multiple tabs, repeated headers/auth, and manual copy-paste of IDs.
they should not be forms for gods sake.
Codeberg.


100s of GBs yes.


yep i got one as well.


Welcome to join us here : https://discord.com/invite/XSYCf7JF4F


Everyone seems to hate this template.
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.