Content and intelligence
Portable content transforms, public feeds, framework delivery, scheduled regeneration, and AI execution context.
These packages help applications transform authored content, publish standards-based documents, and execute AI work without binding domain code to one loader, framework, model provider, or delivery process.
Packages
| Package | Plan | Responsibility |
|---|---|---|
@playstack/content | Loader-independent content transforms and schema helpers. | |
@playstack/content-next | Explicit Pages and App Router content resolution. | |
@playstack/feeds | RSS, Atom, JSON Feed, sitemap, and storage generation. | |
@playstack/feeds-next | Next.js route bindings using Web response primitives. | |
@playstack/nest-feeds | NestJS scheduling, regeneration, and queue consumers. | |
@playstack/ai | Tenant-aware context around the Vercel AI SDK. | |
@playstack/search | Portable mapped lexical search and HTTP contracts. | |
@playstack/search-minisearch | Fuzzy and prefix search through MiniSearch. | |
@playstack/search-next | Next.js App and Pages Router search bindings. | |
@playstack/nest-search | Named NestJS search endpoints and readiness. |
Standards at the center
Content transforms operate on values rather than files. Feed generation emits public standards rather than a Playstack format. AI calls remain Vercel AI SDK calls with Playstack supplying the surrounding tenancy, key, limit, metering, and telemetry context.
Delivery at the edge
Use framework packages only for request, scheduling, and worker integration. Storage clients, route policy, content loaders, and AI providers remain application-owned.