Skip to content
This repository has been archived by the owner on Jan 19, 2023. It is now read-only.

Research and choose API docs engine #5

Closed
linc opened this issue Jun 30, 2016 · 3 comments
Closed

Research and choose API docs engine #5

linc opened this issue Jun 30, 2016 · 3 comments
Assignees

Comments

@linc
Copy link
Contributor

linc commented Jun 30, 2016

Current candidate is Slate: https://github.com/lord/slate

@hgtonight
Copy link
Contributor

Ruby?!?! 😭

@linc
Copy link
Contributor Author

linc commented Jul 1, 2016

The big thing is the end product, especially the tri-column layout of nav > text > examples. We'd also prefer if it accepted Swagger JSON to build, and any other automation that's possible. We've barely looked at it so far. We're pretty agnostic about what these third-party systems run; the new docs engine is Go-based. ¯_(ツ)_/¯

@tburry
Copy link
Contributor

tburry commented Jan 25, 2018

Currently we are using swagger UI and won't be changing in the near to medium term.

@tburry tburry closed this as completed Jan 25, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants