I installed it yesterday, and the biggest issue I’m having is envisioning what a mature project would look like in it. I have not gone looking for examples like that, but if you know of any, i’d love to see some.
hey - thats great :) Happy you downloaded it :) curious to hear your feedback - I will send you a discord link as a message so its not seen as spamming.
Let me see if I understand your question: you mean how Voiden would look when its more mature?
What I am most excited about is that Voiden already does a few things differently from most API tools. Reusable blocks, plain-text everything, and the ability to go from testing to docs to publishing from a single source are already working and shaping how teams can work in a more consistent way.
There is still a lot ahead (for example I want to see what kind of plugins people come up with for the tool, or how AI will eventually play a bigger role) but the principles of Voiden (reusability, composability, plain text, collaboration through git, single source of truth etc.) are the ideas I believe will define and set a new tone/standard of how API tools should be.
I thought no one would ask :) just open sourced it a few weeks ago. But I promise I will never pay someone to praise it pretending to be a developer.
https://github.com/VoidenHQ/voiden
I installed it yesterday, and the biggest issue I’m having is envisioning what a mature project would look like in it. I have not gone looking for examples like that, but if you know of any, i’d love to see some.
hey - thats great :) Happy you downloaded it :) curious to hear your feedback - I will send you a discord link as a message so its not seen as spamming.
Let me see if I understand your question: you mean how Voiden would look when its more mature?
What I am most excited about is that Voiden already does a few things differently from most API tools. Reusable blocks, plain-text everything, and the ability to go from testing to docs to publishing from a single source are already working and shaping how teams can work in a more consistent way.
There is still a lot ahead (for example I want to see what kind of plugins people come up with for the tool, or how AI will eventually play a bigger role) but the principles of Voiden (reusability, composability, plain text, collaboration through git, single source of truth etc.) are the ideas I believe will define and set a new tone/standard of how API tools should be.