Framework integration matrix

Leadtype stays framework-neutral at the core, then exposes thin adapters where a framework has a native routing, prerender, or state convention. The adapters do not render UI components; your app owns markup, styling, and accessibility.

Framework	Human docs route	Agent markdown route	Search helper	Dogfood app
Next.js App Router	`generateStaticParams()` + server component	middleware or `leadtype/next` route handler	`leadtype/search/react`	`apps/next-example`
TanStack Start	catch-all route + generated manifest	server route / Nitro middleware	`leadtype/search/react`	`apps/tanstack`
Nuxt/Nitro	Vue page + Nitro API route	Nitro route or middleware	`leadtype/search/vue`	`apps/nuxt-example`
Astro	`getStaticPaths()`	generated static markdown files, or `leadtype/astro` endpoint in server output	`leadtype/search/client`	`apps/astro-example`
SvelteKit	`+page.server.ts` + `+page.svelte`	`+server.ts` under a `.md` route	`leadtype/search/svelte`	`apps/sveltekit-example`
Fumadocs	`leadtype/fumadocs` source adapter	Next route/middleware pattern	React search helper	`apps/fumadocs-example`

Shared build step

Every reference app generates the same site artifact shape before the framework build:

leadtype generate \
  --src ../.. \
  --docs-dir docs \
  --out public \
  --base-url http://localhost:3000

That writes /llms.txt, /llms-full.txt, /docs/*.md, search JSON, sitemap files, robots files, and /docs/agent-readability.json.

SvelteKit uses the same command shape with --out static because SvelteKit serves static assets from that directory. If your docs are mounted somewhere other than /docs, pass the matching path to the adapter's basePath or artifactBasePath option.

For deployment paths across Vercel, Netlify, Cloudflare, and framework static adapters, see Deploy generated artifacts.

Next.js App Router

Use leadtype/next for static params and page data when you render from a DocsSource:

app/docs/[[...slug]]/page.tsx

import {
  createGenerateStaticParams,
  createLoadPageData,
} from "leadtype/next";
import { source } from "@/lib/source";

const loadPageData = createLoadPageData({ source });
export const generateStaticParams = createGenerateStaticParams({ source });

Use leadtype/search/react in client search components.

Use createGenerateMetadata() for App Router page metadata:

app/docs/[[...slug]]/page.tsx

import { createGenerateMetadata } from "leadtype/next";

export const generateMetadata = createGenerateMetadata({ manifest });

Render JSON-LD from createDocsJsonLd() in the page body; the deployment recipe shows the route-aware snippet.

Use createDocsProxy() when a Next Proxy owns markdown negotiation for the same route tree:

proxy.ts

import { createDocsProxy } from "leadtype/next";

export const proxy = createDocsProxy({ manifest });

TanStack Start

TanStack Start follows the same shape as the flagship dogfood app: generate a route manifest, lazy-load MDX modules by slug, and use leadtype/search/react for search.

Nuxt/Nitro

Nuxt Content is a Nuxt CMS. Leadtype is the portable artifact pipeline: use it when the same source needs framework-agnostic markdown, search JSON, llms.txt, and package docs.

Keep Leadtype source loading and adapter helpers in Nitro server files, not Vue client bundles:

server/api/docs.get.ts

import { createLoadPageData } from "leadtype/nuxt";

const source = await getSource();
const loadPageData = createLoadPageData({ source });

Use leadtype/search/vue for the client search composable.

Astro

Use leadtype/astro to match Astro's getStaticPaths() shape and endpoint signature:

src/pages/docs/[...slug].astro

import { createGetStaticPaths, createLoadPageData } from "leadtype/astro";
import { source } from "../../lib/source";

export const getStaticPaths = createGetStaticPaths({ source });
const page = await createLoadPageData({ source })(Astro.params.slug);

src/pages/docs/[...slug].md.ts

import { createDocsEndpoint, createMarkdownStaticPaths } from "leadtype/astro";
import { source } from "../../lib/source";

export const getStaticPaths = createMarkdownStaticPaths({ source });
export const GET = createDocsEndpoint({ manifest });

Static Astro apps can also serve markdown mirrors directly from the files generated into public/docs. Astro does not need a fake hook. Use leadtype/search/client from a browser script or from any island framework.

SvelteKit

Use the generated artifact manifest for prerender entries, render generated markdown in +page.server.ts, and keep markdown responses in a .md endpoint:

src/routes/docs/[...slug]/+page.server.ts

import { readFile } from "node:fs/promises";
import { renderMarkdown } from "$lib/markdown";
import { manifest, pageForUrlPath } from "$lib/manifest";

export const entries = () =>
  manifest.pages.map((page) => ({
    slug: page.urlPath === "/docs" ? "" : page.urlPath.slice("/docs/".length),
  }));

export const load = async ({ params }) => {
  const urlPath = params.slug ? `/docs/${params.slug}` : "/docs";
  const page = pageForUrlPath(urlPath);
  const markdown = await readFile(`static/docs/${page.relativePath}.md`, "utf8");

  return { html: await renderMarkdown(markdown), urlPath };
};

Use leadtype/search/svelte for store-based client search.

Fumadocs

Fumadocs uses leadtype/fumadocs to map the source primitive into Fumadocs' Source contract. Pair it with the same generated artifact serving used by the Next example.

Verification

The implemented dogfood apps are expected to build in CI:

bun --filter next-example build
bun --filter tanstack build
bun --filter nuxt-example build
bun --filter astro-example build
bun --filter sveltekit-example build