Product Updates

DatoCMS changelog for new features and general improvements
More Options to Customize your SEO Fields
December 20th, 2023

We've introduced two user-friendly features that will enhance your experience with DatoCMS, offering increased customization without added complexity.

In Edit SEO field > Presentation you will find two more options:

Editing an SEO Field

SEO Fields Customization

Choose precisely which fields to display to your editors, giving you the flexibility to focus on what matters most. Choose the fields custom combination of title, description, image, noindex and X summary card:

SEO Field Visible Fields

Example of what "noindex" looks like to editors:

Editing an SEO Field's Visible Fields

Social Link Previews Selection

With our latest update, you can now handpick the social link previews that matter most to your editors, by selecting which previews to display in the SEO field.

In addition to the pre-existing previews for Google Search, Twitter (X), and Facebook, we are also introducing three new previews: WhatsApp, Telegram, and Slack:

SEO Field Visible Previews

Example of the resulting social media card previews for editors:

SEO Field Social Media Card Previews
Content Delivery APINew
Introducing a New 'Prevent Indexing' Option to SEO Fields
December 20th, 2023

We noticed that some users were using custom-made fields to be able to manage robots meta tags preferences at a record level. That is why we decided to introduce it as an enhancement to our SEO field functionality.

Before, you could only set indexing at an environment level, in the SEO Preferences. Recognizing that some scenarios demand more flexibility, we've implemented a "Prevent a page from being indexed by search engines" option also for single records.

This checkbox, available in all SEO fields, empowers developers to seamlessly add a Robots noindex meta tag to pages, offering a nuanced solution for cases not covered by our pre-existing options.

Our CDA _seoMetaTags will return a new Robots noindex attribute if noIndex is enabled either at environment level or record level. Read more about _seoMetaTags, on our CDA documentation.

Editing an SEO Field's Visible Fields
NewUI Improvement
A more visual approach to field editors
December 20th, 2023

In an attempt to enhance the discoverability of the diverse editors available for each field type, we've just rolled out a minor visual tweak to the field editing form.

Now, for all the various editor types that Dato natively offers for each field, there's a small illustration that exemplifies the final result on the content editing side:

In case a plugin that has been installed adds extra editor types, these will be shown in the user interface with a universal Plugin icon:

In future versions of the Plugin SDK we might allow customization of the illustration associated with each field editor... but one thing at a time! πŸ˜‰

NewSecurity
Adding "Force the use of sandbox environments" option to Project Settings
November 28th, 2023

We understand the importance of safeguarding critical environments, and based on valuable feedback from our users, we're introducing a significant enhancement.

With the addition of the new flag "Force the use of sandbox environments" under Project settings > Global properties, admins now have the option block any change to the schema and configuration of the primary environment:

Developers can now work confidently, knowing that destructive actions are disabled, while users still retain the ability to navigate and edit content in the Content and Media Area tabs.

Activating this feature enforces best practices such as migration scripts and sandbox environments, minimizing the likelihood of unintentional changes or footgun situations in production.

UI Improvement
Developer Accessible Area of the CMS Will be English-Only
October 24th, 2023

After receiving feedback from our customers, we have decided to make improvements to our translation approach.

Currently, the entire CMS interface is translated into 15 different languages. However, upon reflection, we realized that this may not have brought significant benefits; in fact, it might have posed some inconveniences.

Our developers' documentation is only provided in English, which means that the DatoCMS glossary and terminology specific to our domain is expressed in English. If the localization settings in the CMS are different, developers may struggle to follow our docs, and find the same entries in the CMS interface.

We also know for a fact that developers are fairly comfortable with English, and translations primarily benefit content writers and editors, who may feel disoriented with English.

As a result, we have chosen to maintain the sections of the app that can only be accessed by developers exclusively in the English language. This includes the Schema, CDA Playground, and Project Settings tabs.

The translation work will also be much easier with the significant decrease in the number of strings to be translated. Our translation process for DatoCMS relies on our wonderful community of users, so if you would like to help us by improving existing translations in your language or suggesting additional ones, please contact us via email. We provide €500 in platform credits for a complete localization.

NewContent Management API
Slug field no longer requires a mandatory reference field
October 12th, 2023

A slug field previously needed a mandatory string field as its reference field. However, from today onward, slug fields no longer enforce this requirement.

No changes have been made to existing slug fields.

The schema UI will continue to suggest using a reference field because it is the most common option, but you now have the ability to uncheck the validation:

New
New validation available: Image Aspect Ratio
October 11th, 2023

A simple but very welcome validation just landed for Single-asset, Asset Gallery and SEO and Social fields: the ability to require a specific aspect ratio for the uploaded images:

By enforcing a specific aspect ratio, you can ensure that all images displayed have a uniform appearance, thus maintaining consistency and aesthetics in the presentation of assets on your website or platform.

UI Improvement
Introducing an improved Navigation System
October 9th, 2023

We're delighted to announce the release of an improved navigation system inside DatoCMS projects. It offers the same simplicity you are familiar with, but with an improved user experience.

Here are the main changes:

βœ… The new Project Settings area lists all the global settings

βœ… Environment-specific configuration happens in the Configuration tab

βœ… Models and blocks are now under the Schema tab

This result comes from our commitment to continuous improvement: it is just the beginning of larger changes, always guided by user testing sessions and your precious feedback.

Content Delivery API
Deep Filtering is officially in public beta
October 6th, 2023

We are excited to announce the public beta release of one of our most requested features: Deep Filtering!

Deep Filtering enables the Content Delivery API to filter records based on the content within their blocks. This functionality is supported in both Modular Content and Structured Text fields.

To learn how to activate deep filtering, and learn everything about the filtering options it enables, please refer to its documentation page.

Webhooks
Introducing Enhanced Webhook Payloads: get more information with less effort!
October 2nd, 2023

We've heard your feedback and understand the frustration of not having, for example, alphanumeric Model IDs included in webhook updates about records.

It makes it difficult to identify the model involved, forces you to make additional API calls, slows down the response.. well worry not, because we have a solution! Please welcome Enhanced Webhook Payloads.

DatoCMS now includes a new key called "related_entities" in the payload of all webhooks. This key contains an array of all the entities that are linked to the main entity (that is, the one that triggers the event itself).

As an example, let's see the new webhook payload sent for a "record update" event:

{
"environment": "foo-bar",
"entity_type": "item",
"event_type": "update",
"entity": { "type": "item", "id": "348295724", ... },
"previous_entity": { "type": "item", "id": "348295724", ... },
"related_entities": [
{ "type": "item_type", "id": "7690234", ... },
{ "type": "user", "id": "69003345", ... },
],
}

Since the Record entity offers relationships with its model and its creator, both objects will be fully included in the webhook payload. This makes it really easy to consume them, and for example, extract the information about the Model ID.

In the case of webhook events caused by changes in Models, the number of related entities will be far larger, as the Model entity offers relationships with all of its fields, fieldsets, etc. Again, very useful data when you need to interact with a model!

We want DatoCMS to be simple and just workΒ©, so we won't be adding any options to enable this behavior. Enhanced Webhook Payloads is already available to everyone, by default.

We hope this new feature saves you time and makes your workflow smoother. Happy coding!