Plasmic CMS out now
Plasmic CMS released
Plasmic CMS is now available to all users! It is a full 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/file upload fields are available.
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.
Plasmic’s CMS is intended as a convenient built-in solution. 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. Stay tuned!
Coming soon: A/B testing, personalization, scheduling
We are currently in the testing phase for the first of our features under the umbrella of “split content.” This includes: multivariate optimization, targeting different variations of your page at different audience segments (based on properties from your website or app), and scheduling different variations over different time ranges. These features are different ways Plasmic empowers you to grow your business faster, and work with performant edge first middleware.
These features will be available for Growth and Enterprise plan customers. If you are interested in getting access to these features, please let us know a bit about your setup here!
Guide to A/B testing with Next.js middleware
We’ve written up a guide to performing A/B testing in Next.js, while taking advantage of the new high-performance edge middleware layer in order to achieve the best of both static generation and dynamic content. Check it out!
By specifying parentComponent in your registerComponent calls, you can organize your components into a hierarchy indented in the insert menu:
Can now use tokens when setting grid gaps.
Grids have min-width applied to their columns to prevent blowouts.
Many more fixes and improvements!