Docusaurus Docs

Minimal docusaurus.config.js:

export default {
  title: 'My Site',
  url: 'https://my-site.example.com',
  baseUrl: '/',
  presets: [
    ['classic', { docs: { sidebarPath: './sidebars.js' }, blog: false }],
  ],
};

Docs-only mode — serve docs at the site root (/) instead of /docs:

export default {
  presets: [
    ['classic', {
      docs: {
        routeBasePath: '/', // docs served at https://example.com/some-doc
        sidebarPath: './sidebars.js',
      },
      blog: false, // disable blog (optional)
    }],
  ],
};

Also add slug: / frontmatter to the doc you want as the homepage, and delete src/pages/index.js to avoid route conflicts.

Monorepo setup — place the Docusaurus site in a subfolder of your existing repo:

my-monorepo/
├── packages/
│   └── my-lib/
├── website/          ← Docusaurus lives here
│   ├── docs/
│   └── docusaurus.config.js
└── package.json

Run the scaffolder from inside the monorepo root:

npx create-docusaurus@latest website classic

In website/package.json, reference local packages directly:

{
  "dependencies": {
    "my-lib": "*"
  }
}

With npm/yarn workspaces in the root package.json:

{
  "workspaces": ["packages/*", "website"]
}

If deploying to Netlify or Vercel, set the Base directory to website/ (or wherever your Docusaurus root is) so the build triggers correctly.

What it gives you

• Docs — versioned documentation with MDX, sidebar, prev/next navigation
• Blog — markdown-based blog with authors, tags, and RSS feed
• Pages — free-form React/MDX pages (landing pages, etc.)
• Theming — swizzleable React components, dark mode, custom CSS
• Plugins — modular architecture; first-party and community plugins
• i18n — built-in localization via CrowdIn or a local workflow
• Search — Algolia DocSearch integration or local search plugins
• Deployment — static output deployable to any CDN/static host

Documentation map