Generate static artifacts

Use this path when your runtime needs files on disk — a CDN-only deploy, a static export, a separate agent-only service, or multiple sibling apps sharing one corpus. The leadtype generate CLI walks your MDX source and writes a complete set of files into public/.

If you'd rather render docs directly from your bundler, see the source primitive. For source-shape decisions (multi-folder, remote git, pinned refs), see Configure docs sources. For host-specific serving details, see Deploy generated artifacts.

The flow

Fetch the source repo

In CI, check out the docs source before the build. For a public repo, a shallow clone is enough:

rm -rf .docs-src/c15t
git clone --depth 1 https://github.com/c15t/c15t .docs-src/c15t

For private repos, use your CI platform's checkout action or a read-only deploy key. The important part is that leadtype receives a normal filesystem path whose root contains docs/.

Lint before generate

Run lint against the fetched docs before writing generated output. Lint fails with file and line context, which is easier to debug than a later app build using stale artifacts:

npx leadtype lint .docs-src/c15t/docs \
  --format github \
  --error-unknown \
  --max-warnings 0

Generate

Point --src at the fetched repo root and --out at the directory you'll serve:

npx leadtype generate \
  --src .docs-src/c15t \
  --out public \
  --base-url https://docs.example.com \
  --json

That command writes:

• public/llms.txt and public/llms-full.txt
• public/docs/*.md
• public/docs/search-index.json and public/docs/search-content.json
• public/sitemap.xml, public/sitemap.md, and public/robots.txt
• public/docs/agent-readability.json
• configured RSS/Atom feeds, such as public/changelog/rss.xml

For feed-specific configuration and date rules, see Generate RSS and Atom feeds.

Use --json in CI so automation can record resolved groups, output files, filters, and search index stats.

Multi-source mounting

Some projects keep docs and release notes side by side instead of putting everything under docs/:

Repeat --docs-dir to include those folders in the same generated corpus:

npx leadtype generate \
  --src .docs-src/c15t \
  --docs-dir docs \
  --docs-dir changelog \
  --out public \
  --base-url https://docs.example.com

By default, extra sources are mounted under /docs/<folder>, so changelog/v1.mdx becomes public/docs/changelog/v1.md and /docs/changelog/v1.md.

Use <dir>=<url-prefix> when the folder should keep its own public route:

npx leadtype generate \
  --src .docs-src/c15t \
  --docs-dir docs \
  --docs-dir changelog=/changelog \
  --out public \
  --base-url https://docs.example.com

That still keeps an internal generated copy at public/docs/changelog/v1.md for search and runtime helpers, but it also writes public/changelog/v1.md and emits canonical links such as /changelog/v1 and /changelog/v1.md in llms.txt, search metadata, sitemap entries, and agent-readability.json.

Add feeds in config when that mounted content should publish RSS or Atom:

export default {
  product: {
    name: "My product",
    tagline: "Developer tools for modern apps.",
  },
  navigation: [
    "index",
    { title: "Changelog", base: "changelog", pages: [{ include: "*" }] },
  ],
  mounts: [{ pathPrefix: "changelog", urlPrefix: "/changelog" }],
  feeds: [
    {
      id: "changelog",
      title: "My product changelog",
      source: { urlPrefix: "/changelog" },
      formats: ["rss", "atom"],
      output: {
        rss: "/changelog/rss.xml",
        atom: "/changelog/atom.xml",
      },
    },
  ],
};

Selected feed pages need stable frontmatter dates. Use explicit date values for changelogs and release notes. For pages where "updated at" should track source edits, default git enrichment writes lastModified when history is available. See Generate RSS and Atom feeds for the full feed contract.

Wire it into the build

Make checkout, lint, and generation run before the framework build:

{
  "scripts": {
    "docs:fetch": "rm -rf .docs-src/c15t && git clone --depth 1 https://github.com/c15t/c15t .docs-src/c15t",
    "docs:lint": "leadtype lint .docs-src/c15t/docs --format github --error-unknown --max-warnings 0",
    "docs:generate": "leadtype generate --src .docs-src/c15t --out public --base-url https://docs.example.com --json",
    "build": "npm run docs:fetch && npm run docs:lint && npm run docs:generate && vite build"
  }
}

If the docs source and docs app live in the same repo, skip docs:fetch and point --src at .:

npx leadtype lint docs --error-unknown
npx leadtype generate --src . --out public --base-url https://docs.example.com

Use library APIs for custom pipelines

The CLI is the happy path. Use the library APIs directly when you need custom plugin order, filters, or generated JSON paths. Keep conversion first — LLM files, search, and Agent Readability artifacts read the generated markdown:

import { convertAllMdx } from "leadtype/convert";
import {
  generateAgentReadabilityArtifacts,
  generateLLMFullContextFiles,
  generateLlmsTxt,
  resolveDocsNavigation,
} from "leadtype/llm";
import { generateFeedArtifacts } from "leadtype/feed";
import { defaultRemarkPlugins, remarkInclude } from "leadtype/remark";
import { generateDocsSearchFiles } from "leadtype/search/node";
import docsConfig from "../.docs-src/c15t/docs/docs.config";

const sourceRoot = ".docs-src/c15t";
const mounts = docsConfig.mounts;

await convertAllMdx({
  srcDir: `${sourceRoot}/docs`,
  outDir: "public/docs",
  remarkPlugins: [remarkInclude, ...defaultRemarkPlugins],
  enrichFrontmatterFromGit: true,
});

await generateLlmsTxt({
  srcDir: sourceRoot,
  outDir: "public",
  baseUrl: "https://docs.example.com",
  product: docsConfig.product,
  nav: docsConfig.nav,
  mounts,
});

await generateLLMFullContextFiles({
  outDir: "public",
  baseUrl: "https://docs.example.com",
  product: { name: docsConfig.product.name },
  nav: docsConfig.nav,
  mounts,
});

await generateDocsSearchFiles({
  outDir: "public",
  baseUrl: "https://docs.example.com",
  mounts,
});

await generateAgentReadabilityArtifacts({
  outDir: "public",
  baseUrl: "https://docs.example.com",
  product: docsConfig.product,
  nav: docsConfig.nav,
  mounts,
});

await generateFeedArtifacts({
  outDir: "public",
  baseUrl: "https://docs.example.com",
  feeds: docsConfig.feeds,
  mounts,
});

const navigation = await resolveDocsNavigation({
  srcDir: sourceRoot,
  baseUrl: "https://docs.example.com",
  nav: docsConfig.nav,
  mounts,
});

Verify

After a clean build, inspect these files:

• public/docs/index.md — converted markdown for the source repo home page
• public/llms.txt — hosted routing index with page-level markdown links
• public/llms-full.txt — all generated markdown docs in one fallback file
• public/docs/search-index.json and public/docs/search-content.json — non-empty search files
• public/docs/agent-readability.json — manifest for markdown responses, JSON-LD, sitemap, and robots helpers
• configured feed files such as public/changelog/rss.xml and public/changelog/atom.xml