🎉 unite cms v0.6 was released today including this 5 new features

Franz Wilding
Aug 17, 2018 · 4 min read
Define complex website layouts with the new variants field.

1. Variants field type

With the variants field you can define multiple variants of fieldsets, your content editors can choose from.Variants fields can be used if you want to create a dynamic content schema, for example a “name” in a CRM: For a company this would be the company name, for a person it would be the combination of a firstname and lastname field:

With the new variants field you can define dynamic content schemas.
Combining a variants field with a collection field allows your contend editors to create complex website layouts.

2. Live preview

One of the headless CMS drawbacks is, that content editors will work with content out of it context (for example on their website). To make it more easy for content editors to see the final result while editing content, unite cms now allows to define an preview endpoint that will get rendered in an iframe next to the update form. The content editor can even switch between three viewport sizes to see how the result will look like on different devices.

Your content editors can see changes while typing in a resizable preview pane.

3. Webhooks

This feature request was on our roadmap from the very beginning and we are glade that we finally implemented webhooks in unite cms. Webhooks are HTTP request to other webservices, that get fired when content was created, updated or deleted. This brings many different possibilities like cache invalidation of a decoupled frontend, triggering static site generator builds (I look at you Netlify).

4. Validations

Starting with version 0.6 you can define custom validations for your content and setting types. Validations (like webhooks) consist of a expression that must be valid and a message that will be shown if not. Inside the expression you can access all the content’s data and define any kind of expressions that must be validated to true.

5. Persist flag for GraphQL mutation API

The final feature we will introduce here is a very small one but will have a big impact: From now on, when using the GraphQL mutation API, you must pass a persist flag that tells unite cms if you want to save the change to the database or not. This allows you to validate content without actual saving it and to test the mutation endpoint. If you are already using the mutation API, please make sure that you include the persist flag, since it is required.

One more thing

With the release of version 0.6, we also want to introduce our new gitter.im channel where you can get help, talk to other developers or suggest new features.

unite cms

Incredible flexible headless CMS built on top of Symfony and GraphQL

Franz Wilding

Written by

Full Stack Software Developer & Founder of unitecms.io

unite cms

unite cms

Incredible flexible headless CMS built on top of Symfony and GraphQL