Problem
Consumers often need sidebars, related pages, filtered views, changelogs, API indexes, and static route params. Today they need to work directly with manifests or source primitives.
Leadtype should expose a typed query API over source metadata and generated manifests without introducing a runtime database.
Proposal
Add a small query API over docs metadata.
Example:
const referencePages = await queryDocs("docs")
.where("group", "=", "reference")
.order("order", "asc")
.all();
const page = await queryDocs("docs").path("/docs/reference/cli").first();Core Behavior
- Query local source metadata at build/server time.
- Support collections.
- Avoid runtime SQL/database requirements.
- Use generated manifests where appropriate.
- Preserve duplicate slug/path validation.
Initial API candidates:
whereorderlimitpathslugallfirst
Framework Integration Notes
Use query results in native lifecycle points:
- Next.js:
generateStaticParams().
- SvelteKit:
entries() and server load.
- Astro:
getStaticPaths().
- Nuxt: route generation/Nitro route data.
- TanStack Start: route manifests/loaders.
Acceptance Criteria
Problem
Consumers often need sidebars, related pages, filtered views, changelogs, API indexes, and static route params. Today they need to work directly with manifests or source primitives.
Leadtype should expose a typed query API over source metadata and generated manifests without introducing a runtime database.
Proposal
Add a small query API over docs metadata.
Example:
Core Behavior
Initial API candidates:
whereorderlimitpathslugallfirstFramework Integration Notes
Use query results in native lifecycle points:
generateStaticParams().entries()and serverload.getStaticPaths().Acceptance Criteria