Where to store your OpenAPI definitions
This post is the first of a series of posts we plan to publish around how organizations can leverage the best of OpenAPI definitions, source control repositories, documentatio...
What Redocly brought to the API space in 2020
Enough said. No doubt, this year will go down as one of the most challenging years in recent times. We hope you are doing ok and have survived this brute of a pandemic.
The top three reasons I love docs-as-code
At Redocly, we embrace developer experience. We believe docs-as-code is the optimal developer experience for producers of APIs.
From ReDoc to Redoc.ly
As you probably know ReDoc was developed by Rebilly which is a payment/subscription company. Their main product is an API and it has a lot of endpoints and advanced payloads.
OpenAPI 3
A few weeks ago, we migrated three API definitions that I maintain and contribute to OpenAPI 3 from Swagger 2. It is relatively easy to transition from version 2 to 3.
API-first design
The background… By the time ReDoc was released in 2015, I was more comfortable with the OpenAPI (fka Swagger) specification.
Hello world, our mission is to perfect the API Developer Portal
ReDoc was born out of frustration with rendering my OpenAPI definitions for API reference docs. Developer documentation is very important to a developer’s experience.