[P2] Create first-class framework integration matrix

[KayleeWilliams]

Problem

Leadtype says "bring your own UI," but users need concrete proof that it works well in each major framework. Svelte/SvelteKit and Astro should be first-class supported targets, not afterthoughts.

The goal is not one generic integration that feels awkward everywhere. The goal is one agnostic core with native-feeling framework recipes.

Proposal

Create a first-class framework integration matrix.

Initial supported matrix:

• Next.js App Router
• Nuxt/Nitro
• Astro
• SvelteKit with mdsvex
• TanStack Start / Vite React
• Fumadocs

Each framework should document:

• MDX/markdown source setup.
• How to render human docs pages.
• How to serve generated artifacts.
• How to serve raw markdown or content-negotiated markdown.
• How to load static search JSON.
• What runs at build time vs server/runtime.

Framework-Specific Expectations

SvelteKit:

• Use +page.server.ts / +page.svelte for human pages.
• Use +server.ts for markdown/API responses.
• Use entries() for prerendered dynamic routes.
• Use stores/runes for client search ergonomics.

Astro:

• Use getStaticPaths() for generated routes.
• Use endpoints for markdown responses.
• Interop with Astro Content Collections where users already use them.
• Use framework islands or plain client scripts for search UI.

Nuxt:

• Use Nitro routes/middleware.
• Use Vue composables for search.
• Position clearly against Nuxt Content: Nuxt Content is a Nuxt CMS; Leadtype is the portable artifact pipeline.

Next:

• Use App Router pages/route handlers.
• Use generateStaticParams().
• Use React hooks for search ergonomics.

Acceptance Criteria

• Each framework has a working render-docs recipe.
• Each framework has an artifact-serving recipe for /llms.txt, /llms-full.txt, markdown mirrors, and search JSON.
• SvelteKit docs include mdsvex setup with Leadtype remark/source plugins.
• Astro docs include getStaticPaths() and endpoint examples.
• Recipes use native framework conventions and avoid generic pseudocode.
• Examples clarify build-time, server-time, and client-time responsibilities.

[pullfrog]

  ^{｜ Build this ➔ ｜ Make a plan ➔}

[coderabbitai]

🔗 Related PRs

#25 - Tighten methodology [merged]
#35 - Add v1 headless integration surface and polish docs [merged]
#37 - Fix type table source root resolution [merged]

---

📝 Issue Planner

_{Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.}

• Create Plan

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!