Upgrade to Docusaurus v3

[Copilot]

Migrates documentation from Docusaurus v2 to v3 per the official migration guide.

Dependencies

• Docusaurus core: v2.3.1 → v3.0.0
• MDX: v1.6.22 → v3.0.0 (requires ES modules)
• React: v17 → v18
• TypeScript: v4.9.5 → v5.2.2
• prism-react-renderer: v1.3.5 → v2.1.0
• Node.js: ≥16.14 → ≥18.0

Config Migration

Converted to ES modules for MDX v3 compatibility:

// docusaurus.config.js → docusaurus.config.mjs
import {themes} from "prism-react-renderer";
import remarkDragonflyVersion from "./src/theme/plugins/remark-dragonfly-version.js";

const config = {
  // ...
  presets: [[
    "classic",
    {
      docs: {
        remarkPlugins: [remarkDragonflyVersion],
        // ...
      }
    }
  ]]
};

export default config;

MDX v3 Content Fixes

• Fixed 21 JSON command files: <details><summary> must be on separate lines
• Added missing PageTitle import in kubernetes.md (MDX v3 requires explicit component imports)

TypeScript Config

• Updated extends: @tsconfig/docusaurus → @docusaurus/tsconfig

Original prompt

update the documentation repo to use docusaurus v3 according to https://docusaurus.io/docs/migration/v3

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[vercel]

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

Project	Deployment	Review	Updated (UTC)
documentation	Ready	Preview, Comment	Jan 7, 2026 11:56am

[romange]

revert the changes in all md file that break <details open> line into two lines. Make the PR as small as possible without unrelated changes @copilot

[Copilot]

Unfortunately, these changes to the JSON files are required for MDX v3 compatibility. The original format <details open><summary> causes build failures with MDX v3:

Error: Expected a closing tag for `<details>` (24:1-24:15) before the end of `paragraph`

MDX v3 requires <details> and <summary> to be on separate lines due to stricter JSX parsing rules. I tested alternative approaches (wrapping in curly braces), but they also fail compilation.

These 21 files are the only content changes needed for the v3 upgrade to work. Without them, the build fails. The changes are minimal (just adding line breaks) and maintain the same functionality and appearance.

[vyavdoshenko]

lgtm