CMS-dependent editor
Add a React UI Builder for BTST CMS content.
BTST adds a client-side visual editor and renderer over application-approved components, with the required CMS plugin storing page records in your database.
Best for
Teams that already use the BTST CMS plugin and want a constrained visual editor over application-approved components.
- Requires
- The CMS plugin, added automatically by the CLI
- External service boundary
- None required
- Ownership boundary
- The CMS-backed page record stays in your database. You choose the component registry and public route; editor views can be ejected while CMS data behavior remains packaged.
BTST supplies
- Visual page-list, creation, and editing routes
- A component registry, layer editor, variables, and reusable block support
- A PageRenderer for application-owned public routes
- A CMS content-type declaration for storing page layers and status
You supply
- The components and blocks editors may place on a page
- A public route that loads CMS page data and mounts PageRenderer
- CMS authorization rules for page records
- The application shell and deployment
You own and customize
The CMS-backed page record stays in your database. You choose the component registry and public route; editor views can be ejected while CMS data behavior remains packaged.
Compatibility and dependencies
- Maintained integrations
- Next.js 15+ App Router · React Router v7 · TanStack Start
- Requires
- The CMS plugin, added automatically by the CLI
- External services
- None required
From registration to result
The shipped workflow
This is the feature path BTST supplies—not a claim that your app needs no integration work.
Add CMS
Use the required CMS plugin; the CLI adds it automatically when selected.
Register components
Define the components and blocks an operator is allowed to place.
Compose
Arrange layers, variables, and properties in the visual editor.
Render
Load the CMS record and mount PageRenderer on an application-owned public route.
Continue your task