Versioned content operations
The generated OpenAPI surface documents authenticated content, media, taxonomy, design and administration operations.
Developer platform
Extend the CMS
without guessing the rules.
Build themes, plugins and integrations against versioned contracts, typed interfaces and explicit compatibility boundaries.
Typed integration foundations
A dependency-free TypeScript SDK provides bounded request, error and idempotency contracts for supported platform operations.
Block-native design packages
Themes declare compatibility and package identity while templates, parts, patterns and global styles remain structured data.
Explicit extension capabilities
Plugin manifests declare runtime compatibility, dependencies and exposed content, taxonomy, editor and API contracts.
Signed delivery with replay boundaries
Operational alert deliveries sign exact bytes, validate destinations, record attempts and dead-letter bounded failures.
Isolation is part of the contract
Tenant identity, authorization, package evidence and network boundaries are enforced below the presentation layer.
Extension lifecycle
A package is more than an uploaded archive.
Marketplace publication requires durable identity and review evidence before a release can become visible or entitled to a tenant.
- 01Declare the manifest
- 02Build an immutable package
- 03Bind digest and compatibility
- 04Complete human review
- 05Publish the approved version
Build on a stronger foundation
Build on contracts designed to stay understandable.
Developer documentation, SDKs and starter packages evolve alongside the APIs they describe.