It'd be very easy to stand up an new instance for the CKAN API and use it for the API docs (I'm happy to take a crack at it and bounce it off you for 👍 ). And adopting this not only makes for good looking api docs, but also helps the agency put forward a more consistent, developer-friendly experience.
The other advantages of it are that it's:
Easy for us to update the CKAN API documentation by embedding the api.data.gov key signup form.
Easy to add a more developer-friendly experience by linking directly to and describing the data.gov CKAN API's endpoints instead of making the user cross-reference the CKAN API docs with the data.gov endpoint.
An increasing number of GSA APIs are normalizing around the user of this opensource API template.
It'd be very easy to stand up an new instance for the CKAN API and use it for the API docs (I'm happy to take a crack at it and bounce it off you for 👍 ). And adopting this not only makes for good looking api docs, but also helps the agency put forward a more consistent, developer-friendly experience.
The other advantages of it are that it's: