Menu
Scheduled publishing

A long awaited feature is finally online! You can now set a future publication date for your items!

Role-based permissions

Your organization’s workflow gets another boost thanks to the ability to let users only manage records created by users with the same role!

Configurable Twitter card

Up until now, all Twitter cards generated by DatoCMS had the twitter:card property set to summary. Now you can change this settings in every SEO field!

You can also configure the stardard Twitter card in the project global settings:

Upgrade to the latest DatoCMS clients to start using this feature on your frontend website!

Save frequent searches as filters

Filters can now be saved and shared between users for easy reuse.

Everyone can freely save personal filters, but only users whose roles allow the creation of shared filters can make them available for everyone:

Add links to external URLs in Navigation bar

You can now add menu items on the sidebar navigation bar pointing to external resources (ie. internal documentation/guidelines, intranets, etc.)

Main locale is no longer required when optional localization is enabled

A long awaited request just shipped! If you have optional translations enabled on one of your models, you are no longer forced to insert content for the main locale:

In-context reordering of navigation bar

You can now move, rename and group your sidebar navigation entries in-context:

Enjoy!

Modular content fields just got better

First of all, you can now set a minimum/maximum number of blocks on Model content fields:

We also enhanced the way Modular content fields are presented. Every block can now be collapsed/expanded:

You can even decide if blocks will start collapsed by default:

Plugins are here!

Plugins aim to provide an amazing experience for DatoCMS editors, by letting developers replace the default fields that DatoCMS provides with third-party HTML5 applications, so the editing experience of every DatoCMS project can be fully customised.

Browse existing plugins, learn how to create new ones or simply read the full announcement in our blog.

Creator-based permissions added to roles

Your organization’s workflow gets another boost thanks to a new feature, the ability to let editors only manage records they created.

Previously as an admin you could set negative or positive permissions specifying which roles can see or edit records discriminating by model and action - ie. can only read or publish etc. Now you can be even more precise by adding a creator-based criteria, that discriminates access to a certain record depending on the fact that the editor is the one that created it.

Creator-based permissions added to roles