Product Updates

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

We're happy to announce that we just shipped some massive performance optimizations in DatoCMS.

If you had projects with lots of languages/modular content blocks, common operations like create/update or publish records could become pretty slow (up to 20 seconds on some edge cases).

We heavily optimized our DB queries, reducing the global execution time by an order of magnitude. Even on extreme scenarios, creating/updating a record should now take not more than 2 seconds.

Happy weekend everyone!

If you need to update/revise some image or media, up until now you needed to upload a new file, hunt down any references to the old media and point them to the new media, then delete the old media. Extremely inefficient and time consuming.

Now you can simply update existing media, retaining all metadata, URL and of course record references:

We just added the ability to specify ISO region-specific language codes to your projects (ie. en-US, zh-CN).

As always, you can change your project supported languages from Settings > Global project settings:

We just shipped the ability to customize the toolbar buttons on multi-paragraph HTML and Markdown fields from the Presentation tab:

In the beginning, a DatoCMS project could only have a deployment environment, the production one. Then, we introduced staging environment. Starting from today, you can setup as many environments as you want and trigger a build of your content on an unlimited number of external services.

This is a great addition for your editorial team, as it can now publish their content on a number of different platforms and let DatoCMS be the unique point where it manages data to be sent everywhere: websites, apps, wearables, you name it.

You can now be notified when one of these actions occur inside a DatoCMS project:

• Create/update/delete/publish/unpublish a record

• Create/update/delete a model

• Create/update/delete an upload (that is, a file or an image in your Media area)

You can also set some filters, so for example you can be notified just when when a record of a specific model (ie. Article) is updated.

Just to give some examples, webhook enable you to:

• Integrate/sync DatoCMS data with third-party systems (Snipcart, Shopify, Algolia, etc.);

• Get Slack/email notifications;

• Automatically post an update on Facebook/Twitter;

• Produce an automatic deploy on your staging environment;

If you don't want to write any integration code, you can use Zapier Webhooks to connect a DatoCMS event with hundreads of different external services, creating any kind of complex automation workflow.

You can read all the details regarding this feature in our documentation page.