Draft
Conversation
|
@egrimstad is attempting to deploy a commit to the Zuplo Team on Vercel. A member of the Team first needs to authorize it. |
|
Preview build of published Zudoku package Warning This PR is from an external contributor. To run the public package build workflow, a maintainer must add the |
Contributor
|
@egrimstad thanks for that. We think this page is a great idea. How do you feel about iterating on this a bit? |
Contributor
Author
Yeah, I could do that. Do you have anything specific in mind? I can look into adding links to terms of service, license and external docs at least. |
4c0846a to
0350b88
Compare
0350b88 to
ef593b9
Compare
Contributor
Author
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.

Draft/Proof-of-concept on how an API overview/information page could look. The reasoning behind adding such a page is that landing directly on a tag can be confusing, and information that is common for the entire API does not have a natural place, (mostly stuff from the
infofield in the specification).Other fields that could be added:
info.termsOfServiceinfo.licenseexternalDocsScreenshot:
