Beginning section for data-driven API section in the docs. #1300
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Built an example and a builder for docs from a json schema
The API section is intended to incorporate API definitions across all products, similar to how Stripe approaches the API reference. We will still have product focused sections in the docs, but that's more driven toward use cases, workflows, and quick starts (all future)
I also have in there an example of how to link to sections inside of a page from the navbar 🔥
NOTE: This is not completely done, but I'm moving off of this for now. The new content is not linked from the primary docs definition, so it's undiscoverable by obscurity
If you want to pull it down and look, you can go to http://localhost:3000/api