Reorganize Epidata API docs to make hierarchy clearer #266
Conversation
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
Akvannortwick
approved these changes
Oct 30, 2020
Contributor
Akvannortwick
left a comment
Akvannortwick
left a comment
There was a problem hiding this comment.
The edits are useful in creating distinctions between API content
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.
Based on comments by @RoniRos about the hierarchy being confusing here, with the site being named Epidata API, containing separate sections for COVIDcast (which is part of the Epidata API) and the Epidata API again.
Preview: http://rosmarus.refsmmat.com/delphi-epidata/
cc @dfarrow0