One of the many things asked for by Swagger users - both newbies and power-users - is a better website around Swagger that makes it easier to learn about Swagger, the specification and tools, best practices, etc. We've finally gotten to a point were we are happy to launch an improved swagger.io on top of our new platform (based on Wordpress and GitHub) which will enable us to build out this content over the coming weeks and months.
Most of the content on this website is actually pulled from corresponding pages on GitHub; you will see a "View Source on GitHub" link on each of them - taking you to the corresponding markdown page on GitHub which you can fork and commit changes to just as before - allowing you to add or correct any content as you see fit (read more about the process at contributing to swagger.io).
Obviously there is still a lot missing here, on the top of our list of content to add we have
- High-level information on how Swagger fits into the API lifecycle
- Best practices for using the spec and the tools in your projects
- Videos/Recording from conferences and meetups
- Information on upcoming releases and related roadmaps
- Information on governance of the Swagger Specification and core tools
- Highlights off different community projects
- Anything you're is asking for!
Dedicated dev team ramping up!
In parallel with building this new website - we are also digging in to build a dedicated development team for the core swagger tools; 5 people are currently ramping up on fixing issues in swagger-core, swagger-codegen, swagger-ui and swagger-js to get the next major release out the door - together with Tony, Ron and myself of course.
Meetups and Swagger Champions
Another activity from our end has been to accelerate evangelising Swagger throughout the API community by both supporting a growing number of Swagger meetups and assembling a group of dedicated Swagger champions - Lorinda will be posting updates so have a look at the announcements page for more details.
Please get in touch - either on the google group, twitter or directly via email - we'd love to hear your thoughts on the next steps for swagger.io and how we can make the api-definition world a better place.
Thanks as always - humbly yours!
/Ole