But how do you collaborate?

Just in case you wanna try it out : https://voiden.md/

We have a very different approach to API tooling.

:)

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

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

but from a programmers perspective - shouldn’t it feel natural - you just keep filling up forms doing the same work again and again?

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.

You are welcome ! Join us here : https://discord.com/invite/XSYCf7JF4F

Voiden’s core request model is based on composable blocks (for elements like headers and auth) that are reusable across requests for a DRY (Don’t Repeat Yourself) approach, unlike Bruno which treats the request as a single, monolithic object that leads to copy-pasting and maintenance burden.

For documentation, Voiden provides living documentation by integrating runnable requests and human explanations side-by-side in the same Markdown file, ensuring it stays in sync with the API, while other tools’ documentation is often separate.

From the monetisation side Voiden: Is an open-source community infrastructure project backed by a different main business, reducing the pressure to monetize aggressively. Bruno is as an open-source project that is under pressure to find a viable monetization strategy, which can lead to license shifts or paywalls.

You can read about the comparison here : https://voiden.md/comparison

Would love some feedback here: https://github.com/VoidenHQ/voiden

That’s a pretty good comparison.

The core idea of executable documentation next to your code is exactly what we were aiming for.

The difference is that Voiden is a dedicated, cross-platform app for the modern ecosystem, bringing the power of that file-centric workflow to everyone. We specifically go further by offering resuable composable blocks for requests (closer to functions than monolithic objects), a unified toolchain for design, testing, and documentation, and a clean, Git-native experience for all developers.

Well having decent documentation is kind of rare.

Thanks for this.

They do !

Here’s how to get started : https://docs.voiden.md/docs/getting-started-section/getting-started/openapi-imports