facebook/docusaurus

Prefer this fork only if its local patches are exactly what you need and you are comfortable owning future upstream merges yourself. For most adopters, upstream Docusaurus is the safer choice because this fork is stale and materially behind current maintenance.

Prefer upstream unless you specifically need the fork's custom React 19, blog, Algolia, Bun, or devcontainer changes and are willing to carry a stale, high-drift codebase.

Choose this fork only if its specific customizations matter more than staying current with upstream. If you want an actively maintained Docusaurus base with the latest fixes, upstream is the safer default.

Prefer this fork only if its specific local changes matter more than staying current with upstream Docusaurus. For most adopters, upstream is the safer choice because this fork is stale and materially diverged.

Choose this fork only if you need its specific local changes and are willing to maintain a large divergence from upstream. If you want the latest Docusaurus capabilities, active maintenance, and easier upgrades, upstream is the safer choice.

Choose this fork only if its added compatibility and customization work matches your needs and you are willing to maintain a substantially older, heavily diverged Docusaurus branch. For most adopters who want the newest upstream fixes and a lower-maintenance docs platform, upstream is the safer default.

Prefer this fork only if you need its specific older baseline and local compatibility changes. If you want current upstream reliability, security fixes, and low-maintenance adoption, upstream is the safer choice.

Choose this fork only if you want its specific downstream changes and can accept substantial upstream drift. For most adopters, upstream Docusaurus is the safer choice because this fork is stale and likely missing many recent fixes and features.

Choose this fork only if its local changes are exactly what you need and you are comfortable maintaining a large upstream gap. If you want the latest Docusaurus improvements and lower long-term upkeep, upstream is the safer default.

Choose this fork only if its specific compatibility additions match your needs and you can own the maintenance burden. If you want the safest path for a general Docusaurus site, upstream is the better default.

Prefer this fork only if its specific downstream changes are already what you need. For most adopters, upstream is the safer choice because it is actively maintained and this fork is both stale and materially diverged.

Choose this fork only if its added React 19, Node 22, Algolia, and authoring changes are specifically valuable to you and you can own maintenance. If you want a current, lower-risk Docusaurus base, upstream is the better default.

Adopt this fork only if its older customization set is directly valuable and you can own the maintenance debt. For most new users, upstream Docusaurus is the safer choice because this fork is stale and materially behind current fixes and compatibility work.

Choose this fork only if you need a frozen, customized Docusaurus snapshot and are prepared to maintain it yourself. If you want current features, active fixes, and lower maintenance risk, upstream is the better default.

Prefer upstream unless you specifically need this older v2 behavior set. This fork is most suitable for legacy sites that value stability over features; for new adopters, the maintenance gap and missing modern improvements are the main reasons to avoid it.

Choose upstream unless you specifically need a legacy Docusaurus snapshot. This fork is only attractive if your priority is preserving old behavior or an existing customized branch; otherwise the maintenance and compatibility risk is high.

Choose this fork only if you specifically need its frozen 2022-era behavior or custom internal workflow. For most adopters, upstream Docusaurus is the better choice because this fork is stale, materially divergent, and likely missing many years of fixes and ecosystem support.

Prefer upstream unless you explicitly need this older beta-era customization set; the fork is stale and looks more useful as a historical/customized snapshot than as a base for new work.

Prefer this fork only if you need the older v1 behavior or its bespoke edits and are willing to own the maintenance burden. If you want an actively supported documentation framework, upstream is the better default.