Custom controls, CMS write API, and more

Custom controls for code components

You can author custom controls for your code components!

This means that in addition to the built-in types of controls that you can show in the right sidebar for code component props, you can now show arbitrary UI there as well. Simply provide any React component to render.

This includes the ability to pop out modals for more detailed configuration UI on click.

Custom controls represent a significant step in letting you truly customize and extend the platform. Check out the docs to learn more!

Default components for templates

Projects now have a notion of “default components.” The first use case for this is in templates.

You can specify default components for the following kinds: Button, Checkbox, Select, Switch and Text Input. 

All Plasmic projects come with the ability to insert a built-in version of each of these types of components. But you don’t have to use these Plasmic built-in components—you can now leverage the default components system to designate your own choice of components (such as from your org’s design system) to replace the built-in ones in Plasmic.

For example, if you designed your own Button component, you can designate that as the default Button component for your project. This way, users in the Plasmic project will only see your Button component and not the Plasmic built-in Button component.

Another use case is code component templates. Developers have been able to make code components come with a more complete example template, to make it easier for editors to use the code components. (These are defaultValues for slots.)

Within these templates, you can now include instances of a project’s default components.

See the full API reference docs to learn more:

CMS write API

The Plasmic CMS write API is now fully documented.

With the write API, you can now perform programmatic and batch updates to your CMS content using a secret admin API token that you can obtain from your CMS settings page.