The /docs site uses Pagefind for full-text search. Pagefind is a static search library that builds an index at build time — no server process is required to serve search results.
Build step
The search index is generated during pnpm build, which runs:
next build && pagefind --site .next/server/app --output-path public/_pagefindnext buildcompiles the Next.js application, including all MDX documentation pages undercontent/.pagefind --site .next/server/app --output-path public/_pagefindcrawls the compiled HTML output and generates a static search index inpublic/_pagefind/.
The public/_pagefind/ directory is gitignored — it is build output and should never be committed.
Search scope
Pagefind indexes only the /docs section (the Nextra documentation site). App pages (/, /account, /{org}/, etc.) are not indexed.
Search covers all documentation sections: Getting Started, Architecture, Frontend, Backend, Scoring, Database, Infrastructure, Guides, Contributing, and Troubleshooting.
In development
Search is not available in pnpm dev mode. Pagefind only runs during the production build.
To test search locally:
pnpm build && pnpm startThen open http://localhost:3000/docs and use the search bar.
In production
On Vercel, the full pnpm build command runs as the build step. The generated public/_pagefind/ is included in the deployment. Search is available on the deployed site without additional configuration.
CI
The CI build step runs the full pnpm build command, which includes Pagefind. This verifies that search indexing succeeds as part of every CI run.
Configuration
Pagefind uses default settings. The output path (public/_pagefind) is served as a static asset by Next.js without additional configuration. No pagefind.json or custom config file exists — all options are passed as CLI arguments in the build script.