Update docs template #290
Merged
Update docs template #290
Conversation
This file contains 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.
In gh-pages I have manually created a
_pydoop1subdir to keep the v1 docs for future reference (we might drop them when we feel no one needs them anymore). This PR updates the docs template by adding a reference to the v1 docs. Before moving them to the subdir, in turn, the v1 docs have been altered to also include a back reference to the main (latest) docs.I have also included a hotfix for the version string (the docs still had "2.0.0-alpha1" from a previous iteration).
gh-pageshas already been pushed, so the effects of this PR are live at https://crs4.github.io/pydoop.