Getting Back To Work On My OpenAPI Toolbox02 Mar 2017
I used to have a Github repository dedicated to Swagger tooling and implementations, but I took it down after Swagger was donated to the Linux Foundation. I've rebooted it as my OpenAPI Toolbox, providing a single Github repository for managing an active list of open source tooling built on top of the OpenAPI specification.
Here is a snapshot of my toolbox of OpenAPI-driven solutions, as it stands today. This site is a Jekyll-driven website running on Github, using Github Pages. The tools in this toolbox are driven by a YAML file in the _data folder for this repository, with the HTML pages driven using Liquid.
Here are the tools organized by type of implementation (something that is evolving quickly):
Here they are organized by programming language, providing another dimension to look at the tooling being developed on top of OpenAPI.
This project is forkable using the Github repository, and accessible as JSON. If you have a tool you think should be added, or there is something that needs fixing, you can submit an issue on the Github repository, or submit a pull request. It is meant to be a community project, designed to be forkable, shareable, and machine-readable.
I've just started adding the tools I have in my database. I only have 37 so far, but will be adding more as I have time. Once I have it up to date, I will start thinking about other ways to slice and dice the tools, to better understand what is being built on the OpenAPI specification, what tools are being built on the upcoming 3.0 version, as well as working to identify where the gaps and opportunities are for developing tooling.