By default, all GraphQL queries on paginated items to our Content Delivery API return a response of 20 items.

While we'll still retain this as the default behaviour, we've increased the maximum number of items to 500.

You can manage this behaviour when making your queries using the first parameter like this:

1
{
2
# Fetch the first 500 posts
3
  allPosts(first: 500) {
4
    id
5
    slug
6
    title
7
    description
8
    publishedAt
9
    content
10
  }
11
}

For more info on working with Pagination in DatoCMS check out the docs.

Handling complex user roles and permissions is complicated enough as it is, so we thought we'd try and simplify things on our end as much as possible!

Firstly, when creating highly specific and granular roles that are inherited from others, you'll see a cleaner and clearer indication of which permissions are inherited from parent roles.

While you're in the process of making any modifications or edits to them, we're also showing a new pill that explicitly highlights what's changing, so you can make sure everything's good before hitting save.

On the cosmetic side, we're also making it way easier to just understand the roles you're working with. Inside Content Permissions, all the rules are now shown as actual readable sentences instead of "disabled form fields" which are just so much more readable!

As one of the most used and installed plugins in the DatoCMS Marketplace, this update was long overdue.

You can now update this plugin to V1.0.24 which introduces custom breakpoints for desktop, mobile, and tablet, allowing your editors to preview Draft and Published content within the CMS for each device.

Install the plugin via the Marketplace. If you already have it installed, you can head on to Configurations > Plugins and click to Update the plugin to the latest version.

A new enhancement has just been released that should allow for easier investigation of any issues encountered with the indexing of pages by our Site Search functionality.

By opening the details of events labeled "Site spidering completed with success", it is now possible to access a detailed log of the operations performed by our crawler, including analysis of the robots.txt and any sitemaps.

At the end of the log, you will also find a handy list of pages that encountered indexing problems.

Another one for content best practices! We're rolling out an option to stop CMS users from publishing invalid records.

How can published records be invalid you ask? Imagine records where title fields were required, and everything was published correctly. No sweat. You now extend that model to add in a new subtitle field which is also required. At this point, all the records in that model will require you to update them by filling in the subtitle field before their next publish.

While we'll enable this flag to TRUE for all new projects, you can easily enable it in your existing project under Configuration > Available Updates.

We’ve made a small but significant change to the way new models are created.

To enforce editorial best practices and provide better flexibility for your content workflows, draft mode will now be enabled for all new projects. While this is the new default, you are able to override this when creating new models, under the model's validation settings.

Additionally, for existing projects, we’ve added an option to enable this setting. You can find it in Configuration > Available Updates.

It is now possible to save invalid records in their draft state, and postpone validation enforcements to publication time. The feature can be enabled and/or disabled on models with the draft/published stages active.

The feature affects the CMS and, of course, the CMA (Content Management API). When draft saving is active, it's possible to POST/PUT invalid records to CMA and have them saved: the endpoints respond with a 200, and the record is just saved as a payload.

Validations will take effect when the record is published. If the record is not valid, publication fails, and editors need to fix the content to ensure all rules are handled before proceeding to move the record into the Published stage.

Starting March 10th, 2025, our legacy batch operation endpoints — which have been deprecated for years — will be discontinued and will return error responses. Documentation for these endpoints can be found here:

• https://www.datocms.com/docs/content-management-api/resources/item/batch_destroy

• https://www.datocms.com/docs/content-management-api/resources/item/batch_publish

• https://www.datocms.com/docs/content-management-api/resources/item/batch_unpublish

Required action

If you're using any of these endpoints, please update your integration to use their replacements. Documentation for the current endpoints can be found here:

• https://www.datocms.com/docs/content-management-api/resources/item/bulk_destroy

• https://www.datocms.com/docs/content-management-api/resources/item/bulk_publish

• https://www.datocms.com/docs/content-management-api/resources/item/bulk_unpublish

Impact assessment

Based on our monitoring over the past two months, only four projects are actively using these deprecated endpoints. If your project is affected, you will receive a direct email from our team in the coming days.

We’ve redesigned the Plugin installation experience to make discovering and installing plugins from the marketplace faster and more intuitive—directly within your DatoCMS project.

How It Works

To add a plugin, go to Configuration > Plugins and click on Add a new plugin. This opens the Marketplace, where you’ll find all community plugins displayed as detailed cards, giving you essential information at a glance.

Clicking on a plugin reveals its detailed view, including its description, metadata, and additional information. From there, simply click the Install button to start using your plugin immediately.

What's hot and what's not

We’ve introduced brand new collections to make it even easier for you to pick and choose relevant plugins for your project!

Editor Favorites to showcase plugins that enhance the content and editorial workflows with commonly used plugins loved by editorial teams.

Dev Favorites to highlight the most commonly installed plugins by project owners to make daily operations and new features easier to manage.

Enterprise and Workflows to curate common plugins for security, compliance, and custom third party integrations used by teams of larger sizes.

We weren't too happy about the inconsistencies and the discoverability of the expand/collapse actions with sidebar interactions in the CMS, so we've released some improvements.

The sidebar component retains it's open/closed states, and we've redesigned the component to have consistent interactions with instant transitions.

This change is reflected on all sidebars to the left and right of screens on content views, asset views, plugins, and within the project settings.