Open
Conversation
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
janechu
force-pushed
the
users/janechu/replace-docusaurus-with-11ty
branch
from
bfcc641 to
9678562
Compare
chrisdholt
approved these changes
Feb 6, 2026
Member
chrisdholt
left a comment
chrisdholt
left a comment
There was a problem hiding this comment.
Much simpler and hopefully with far less issues.
2 tasks
This file contains hidden or 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
2 participants
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.
Pull Request
📖 Description
This change replaces Docusaurus, which has been causing a multitude of dependency issues, with 11ty.
👩💻 Reviewer Notes
Please review carefully, I have separated versions into 1.x and 2.x folder which should make this easier for our v3 migration.
There are a couple scripts for navigation, and the CSS has been copied over, there may be some unused CSS at present but I believe it can be cleaned up relatively easily at a later date.
✅ Checklist
General
$ npm run change