ask-user-help-docs

Create an MDX file with title and description frontmatter in content/docs, then add its slug to meta.json. Ordering comes from meta.json, not the filesystem, so a page missing from meta.json will 404.

The host's Tailwind entry is not scanning fumadocs-ui/dist. The preset's @source inline lists are dropped by Vite's CSS import handling, so you must add explicit @source directives for fumadocs-ui/dist and the package's own src directory.

Not with its standard codegen or runtime compilation. Workers have no filesystem to scan and forbid code generation from strings, so content must be inlined with import.meta.glob and MDX compiled at bundle time via a Vite plugin.

Something compiles MDX at request time using new Function, which workerd rejects with EvalError: Code generation from strings disallowed. Move compilation to the bundler with helpDocsMdxPlugin() registered in the Vite config.

Search structured data is computed by structure() over the raw body at index time, so a page whose body failed to compile indexes empty. Also verify the search route matches docsConfig.searchApi.

The host's Vite or Vitest config is missing helpDocsMdxPlugin(). The plugin must be registered in both configs so the eager import.meta.glob of MDX files resolves to compiled modules.