We just made possible to specify which API endpoints an API token can access:

This will prevent from using your ie. production API token to read temporary/draft content using the GraphQL preview endpoint.

On February 4, at 11:00 CEST we'll publish a small change to the GraphQL types of our Content Delivery API.

If you want to get the value of a field for every locale of the project, you can use the following query:

query {
  allBlogPosts {
    _allTitleLocales {
      locale
      value
    }
  }
}

Right now the type for the _allTitleLocales field is [PageModelSlugMultiLocaleField]. After the change, the name of the type will simply be [SlugMultiLocaleField]. That is, the prefix {MODEL_NAME}Model will be dropped.

This change will drastically reduce the overall number of GraphQL types on multi-language project, reducing both our response times (by up to ~25%) and time to process the schema on your side.

The large majority of our users won't need to do anything, but if your codebase do relies on GraphQL type names, please make sure to do the necessary adjustments before February 4 or contact us if you need more help/information.

We've just made possible to see the log of a Netlify build related to a DatoCMS publication from under the Activity Log section of your administrative area:

Quite handy to quickly investigate why some build failed without having to leave the DatoCMS interface!

We've just pushed a new version of our JS and Ruby clients that will automatically retry requests after the correct amount of time if they encounter a 429 Too Many Requests response from our Content Management API when exceedings rate limits.

Upgrade your projects to the latest version of our clients to take advantage of this!!

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

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

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: