docs(v2): recommend Docusaurus 2 usage #3785
Merged
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
slorber
added
the
pr: documentation
|
Deploy preview for docusaurus-2 ready! Built with commit c393aed |
|
Size Change: +16 B (0%) Total Size: 153 kB ℹ️ View Unchanged
|
lex111
reviewed
Nov 19, 2020
lex111
approved these changes
Nov 21, 2020
|
@slorber thanks! |
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.
Motivation
It has been reported that some parts of the doc let people think versioning is not supported yet.
Versioning is working fine now, and i18n is coming soon.
We should now drive more users to start on v2 than v1, despite v2 still being in alpha (not for long), even if they need i18n support.
Note: most users are already using v2 anyway: