Build an MDX directory into a static React documentation site. Doctrine provides a Vite development server, prerendered HTML, Pagefind search, localized navigation, light and dark themes, and subpath-safe assets without requiring a production Node.js server.

• Node.js 20.19 or newer.
• A native target supported by @amamo/mdx. Doctrine has no JavaScript fallback for MDX compilation.
• Trusted content and configuration authors. MDX, referenced TSX pages, config files, navigation files, and custom components can execute JavaScript during the build.

Install Doctrine with your package manager:

Then create the content directory:

mkdir docs

Create docs/index.mdx:

# My documentation

The first page is ready.

Create docs/meta.ts to make the page part of the navigation:

import { defineDirectory } from '@amamo/doctrine'

export default defineDirectory({
  items: [{ page: 'index', title: 'My documentation' }],
})

Preview and build:

doctrine dev docs
doctrine build docs --site-url https://example.com/project/

Development defaults to http://localhost:5173. Production output defaults to dist; pass the real public URL so assets, canonical links, locale routes, search results, and 404.html use the correct deployment base.

doctrine.config.ts is optional. Add it at the project root when the defaults are not enough:

import { defineConfig } from '@amamo/doctrine'

export default defineConfig({
  title: 'My project',
  description: 'Guides for My project.',
  githubUrl: 'https://github.com/your-org/my-project',
  pageActions: true,
  copyright: 'Copyright © 2026 Your organization.',
  locales: {
    default: 'en',
    names: ['en', 'zh-CN'],
    labels: { en: 'English', 'zh-CN': '简体中文' },
  },
})

Locale variants use filename suffixes. Every directory with content for a locale also has the matching navigation module:

docs/index.mdx
docs/meta.ts
docs/index.zh-CN.mdx
docs/meta.zh-CN.ts
docs/guide/install.mdx
docs/guide/meta.ts
docs/guide/install.zh-CN.mdx
docs/guide/meta.zh-CN.ts

The default locale uses /guide/install/; the translated page uses /zh-CN/guide/install/. Navigation modules own page titles, icons, child directories, and order.

By default, each MDX document route also exposes its authored source at the corresponding .md URL. For example, /guide/install/ has /guide/install.md, while the translated page has /zh-CN/guide/install.md. Document pages provide Copy Page and View as Markdown actions. When githubUrl is configured and the repository-relative source root can be inferred or is set with githubSourceRoot, Open in GitHub targets the actual locale source on the repository's default branch. The .md response is the original MDX rather than Markdown rebuilt from HTML, so it can include frontmatter, imports, and JSX. Set pageActions: false to disable both the actions and .md output without removing the GitHub link in the header.

A page entry can also name a same-directory .tsx file. Only TSX files listed by the matching locale navigation module become routes; every other TSX file remains an ordinary component. These pages render inside Doctrine's header and footer without the documentation sidebar, prose layout, table of contents, page actions, or a generated .md source route.

CLI + doctrine.config.* + meta*.ts
  -> normalize paths, URLs, locales, and navigation
  -> Vite + @amamo/mdx compile content, heading metadata, annotated code, and client/SSR bundles
  -> React prerenders every navigation route
  -> Doctrine writes HTML, authored MDX sources, assets, and 404.html
  -> Pagefind indexes the final HTML

Doctrine keeps the generated content registry and cache records in .amamo-mdx/, and temporary build work in .doctrine/. Treat both as generated directories and keep them out of version control.

• Getting started
• Features and runtime behavior
• Customization
• MDX components
• Configuration
• CLI reference
• GitHub Pages deployment

See CONTRIBUTING.md to work on Doctrine itself.

MIT