Skip to content

update theme for docusaurus 3.10#62

Open
nicoalba wants to merge 2 commits intomainfrom
docusaurus-310
Open

update theme for docusaurus 3.10#62
nicoalba wants to merge 2 commits intomainfrom
docusaurus-310

Conversation

@nicoalba
Copy link
Copy Markdown
Contributor

@nicoalba nicoalba commented Apr 8, 2026

Docusaurus 3.10 compatibility — theme package

What this does

Updates the shared theme package (@netfoundry/docusaurus-theme) to be compatible with Docusaurus 3.10.

The one real change

Removed useKeyboardNavigation from NetFoundryLayout.tsx — this hook was removed from Docusaurus's internal API in 3.10. The behavior (detecting keyboard vs. mouse navigation for accessibility focus rings) is now handled automatically inside LayoutProvider, which NetFoundryLayout already wraps every page with. No visible change for users.

Version bumps

  • packages/docusaurus-theme/package.json — devDeps remain at ^3 (any Docusaurus 3.x)
    packages/test-site/package.json — pinned all @docusaurus/* packages to 3.10.0 so the test environment matches the version being validated

Why this is paused

The test-site uses redocusaurus, which pulls in older Docusaurus transitive dependencies that conflict with 3.10. Working around it required a resolutions block in the root package.json that Clint flagged as potentially overly aggressive. Waiting a few weeks to see if redocusaurus releases a 3.10-compatible version, which would make that workaround unnecessary and keep the changeset minimal.

Next steps after merge

  1. npm version patch + npm publish to release updated theme
  2. Go through each doc repo (platform-doc, ziti-doc, k8s-on-prem, zrok, unified-doc) — fix admonition syntax + upgrade @docusaurus/* packages in one PR per repo

@vercel
Copy link
Copy Markdown

vercel bot commented Apr 8, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
docusaurus-shared Ready Ready Preview, Comment Apr 8, 2026 10:08pm

Request Review

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant