Replace API documentation redirect with redirect-from #11
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.
#10 didn’t work, because it depends on a publishing tool that isn’t present on GitHub Pages. Instead, this PR uses a whitelisted jekyll plugin to create the redirect. I’ve tested this locally to verify that it works with jekyll.
Each time a new release is published,
redirect_from
must be removed from the old version and added to the new version. Alternatively, we could have index.html be a simple HTML page with a meta redirect. @danpat @daniel-j-h, which approach would you prefer?