Use with Plasmic CMS or third-party CMSes
Plasmic has a full built-in CMS. This is an API-first headless CMS, but directly integrated into Plasmic’s visual editor, letting you drag and drop structured content directly into your designs.
Whereas Plasmic Studio is for visual layout and design, the CMS is for organizing structured records of data into database tables called models (in CMS terminology). The two work together—so after creating (say) a set of blog posts, testimonials, case studies, or other homogeneous content in the CMS, you can drag and drop this data directly into your pages with arbitrary layout and design.
Some headline features:
- Drag and drop CMS data into your designs (via the component store).
- Versioning: full edit and publish history.
- Image and file upload fields.
- Headless API for rendering content anywhere, and API creating/updating content.
All teams, including free-tier teams, will be able to create and access a CMS database. Developer roles on a team are able to define the model schema, and content creator roles can populate these with the content entries.
See also the Plasmic CMS API documentation.
Note you can fork and extend the code components in the component store, if you have more advanced schemas or rendering logic.
Want to use a third-party CMS? We also have first-class integrations coming soon for other leading content stores we’re proud to partner with. This includes:
Note that there is no special treatment of Plasmic’s built-in CMS in this regard—all data integrations (including Plasmic CMS) are implemented as normal code components. Plasmic is unopinionated about where your data comes from in order to be a truly open and flexible visual builder.
And as always, you can fork and customize these code components—see for instance the Plasmic CMS code components. Forking and customizing can be especially helpful if you have more advanced schemas or rendering logic that you need.
Learn more about data integrations in general.