A lot of developer tools follow the same pattern: They start simple and then new ideas come. Then these these new ideas become built-in features.
This is of course fine (and natural) but over time, the core can become huge, harder to maintain and evolve, and slower to experiment with.
When we started building Voiden we wanted to avoid this trap.
What we observed from our experience and also while talking to other developers is that different teams use API tools very differently, in different scenarios.
So we decided that forcing everyone into the same giant feature set doesn’t really make sense.
So, instead of putting everything in the core, we decided to have the tool grow through a plugin system. This way, it can be flexible and extensible since new functionality can live outside of the core tool.
The idea is simple:
Keep the core lean. Let the ecosystem grow around it. Developers can build extensions independently and users can just install the pieces they actually need.
Keeping Voiden flexible and extensible is one of the key design principles we had from day one and I am very happy with this milestone.
Curious what kinds of extensions people will build 🙂 (we already have a few community plugins in the works)...
Start contributing: https://docs.voiden.md/docs/plugins/build-a-plugin
Repo here: https://github.com/VoidenHQ/voiden
Top comments (0)