Product Updates

DatoCMS changelog for new features and general improvements
August 28th, 2018
Fetch all the language values for a field in a single call
Content Delivery API

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 {
August 24th, 2018
Records creation just became up to 10x faster
Content Management API

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!

August 17th, 2018
Update media in place

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:

August 9th, 2018
Region-specific language codes

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:

August 7th, 2018
Customizable toolbar for HTML and Markdown editors

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

Customize toolbar buttons

August 2nd, 2018
Multiple deployment environments

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.

August 2nd, 2018
Webhooks now available!
NewAPI Clients

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.

June 28th, 2018
Optional translations now available!

You can now configure a certain model so that you are not forced to insert content for every language your administrative area supports, but just for the primary one, and then manually add additional locales on a per-record basis.

This allows use cases such as multi-language blogs, where some articles can be written only in English, other only in Italian and others in both languages.

You can enable optional translations in your Model settings:

This will be the result for the editor:

June 27th, 2018
Released v0.5.4 of JS client
API Clients

We just rolled version 0.5.4 of our JS client!

The big change is that the methods the client makes available are generated at runtime based on the JSON Schema of our CMA. This means any new API endpoint — or changes to existing ones — will instantly be reflected to the client, without the need to upgrade to the latest client version.

We also added a new deserializeResponse option to every call, that you can use if you want to retrieve the exact payload the DatoCMS returns:

import { SiteClient } from 'datocms-client';
const client = new SiteClient("YOUR-API-KEY")
// `deserializeResponse` is true by default:
const accessToken = client.accessTokens.create({
name: "New token",
role: "34"
// {
// id: "312",
// hardcodedType: null,
// name: "New token",
// token: "XXXX",
// role: "34"
// }
// if `deserializeResponse` is false, this will be the result
const accessToken = client.accessTokens.create(
name: "New token",
role: "34"
deserializeResponse: false
// {
// data: {
// type: "access_token",
// id: "312",
// attributes: {
// name: "New token",
// token: "XXXX",
// hardcoded_type: nil
// },
// relationships: {
// role: {
// data: {
// type: "role",
// id: "34"
// }
// }
// }
// }
// }

In our doc pages we also added some examples for the super-handy allPages option which was already present since v0.3.29:

// if you want to fetch all the pages with just one call:
client.items.all({ "filter[type]" => "44" }, { allPages: true })
June 18th, 2018
Released gatsby-source-datocms v1.1.9
API Clients

We just added support for the new Gatsby v2 fixed and fluid responsive image queries.

Old names (sizes and resolutions) are deprecated but still work.