[DO NOT MERGE] very rough POC of multi-version docs #904
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
… sometimes camelCase 🤷
|
Closing as this is just for reference. |
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.
I'm not planning to merge this. It's a rough outline of what it would look like to have most of the docs using one version scheme, and a single section using a different version scheme.
I'm creating this PR as a reference point, and will close it immediately.
Before you click on "Files Changed", this is a better way to view the diff.
Most docs show versions 1.3 and 1.2:
One new section named "community" was added, with versions 5 and 5.1:
Note that the URL for this new community section starts with "/community" instead of "/docs". This is what it looks like with multiple docs instances configured.
(The list of files changed is massive, as I cleared out a whole bunch of docs so I could focus on the problem at hand. If your browser is slow while viewing this PR, that's why. This is a better way to view the diff.)