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!

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:

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

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:

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

Enjoy!

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 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.

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.

We just added the ability to present DatoCMS records in a table, with the ability to completely configure the columns (add, remove, reorder and resize).

The classic "compact" visualization mode is still the default, so if you want to switch to this new mode head over one of your models and change it to "Tabular view":

As requested on Slack, we just introduced a new way to fetch content on our GraphQL Content Delivery API.

If you want to get the value of a field in every language, you can now use the _all<FieldName>Locales field:

query {
  allBlogPosts {
    _allTitleLocales {
      locale
      value
    }
  }
}