-
Notifications
You must be signed in to change notification settings - Fork 193
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Prepare for docusaurus v3 #2719
Comments
I saw they anticipate releasing V3 in the next few days unless something big comes up. |
I'm glad to see they acknowledged the MDX upgrade and infrastructure changes were the bulk of this release. I did see two interesting features highlighted: I don't know how much we'll be able to do with code blocks, but I'm a sucker for interactive experiences. I didn't realize ☝ I'll create two issues for the draft and unlisted content, respectively. I'd like to see us incorporate a strategy for using the draft feature and then when we move to V3, a strategy for using unlisted. |
This came up during our 8.4 docs retro as a possible idea to explore to keep our build times down. |
Here is a dump of the |
https://docusaurus.io/blog/preparing-your-site-for-docusaurus-v3
There is anecdotal data from the write-the-docs slack that performance is improved in v3.
Tasks
The text was updated successfully, but these errors were encountered: