Content and CMS APIs
These packages support the optional content capability. Use their declarations to keep provider data, registered types, layout selection, and authoring schemas aligned.
How the pieces fit together
| Package | Contract |
|---|---|
| Content extension | Descriptors, builders, layouts, actions, and conditions |
| System content feature | Built-in content types and configurations |
| Sanity provider | Fetching, local cache policy, media URLs, and live content |
| Sanity client | GROQ queries and transport configuration |
| Portable Text | Structured text models and render builders |
| Embedded content | Content binding and widgets inside an existing app |
| Authentication content | Forms and configurations using the auth capability |
| Onboarding content | Steps and their default layout |
| Developer tools | Registry inspection and previews |
| Widgetbook | Preview adapters |
| Schema packages | TypeScript authoring contracts |