We're introducing favorite locales to keep your workspace focused and your most-used languages instantly accessible.

What's New?

Mark up to 6 locales as favorites to prioritize them across the CMS, reducing clutter and eliminating the need to hunt through long language lists.

• Instant access: Favorite locales appear at the top of selectors throughout the CMS — no more hunting through lists.

• Cleaner workspace: While editing records, collapse non-favorite locales to keep your view focused on what matters.

How Does It Work?

Open Editor's Preferences from your avatar menu (upper right corner), enable "Favorite Locales," and select your most-used languages. You can choose up to 6 favorite locales.

Why Does It Matter?

Managing 10, 15, or 20+ locales means constant scrolling and visual noise. By surfacing only the languages you use regularly, this feature eliminates friction in your daily workflow — especially valuable when you work primarily in a consistent subset of locales. You get faster navigation and a cleaner interface without changing how localization works.

We recently removed the ability to add new Travis CI and CircleCI build triggers: these integrations have been practically unused for years. Maintaining them creates technical debt and maintenance burden without providing value to our users.

Existing Travis CI and CircleCI build triggers will be migrated to custom build triggers in the following weeks. After the migration is complete, the migrated CircleCI triggers will be fully functional — both outbound triggers and incoming webhooks continue to work seamlessly. For Travis CI triggers, that have not been used in the last 6 years, we'll continue to manage outbound triggers, which will still work, while incoming webhooks won't be recognised as valid.

We'll contact all paying customers with existing Travis CI and CircleCI build triggers via email to inform them about the incoming changes. 

We've added native LLM.txt support to make our documentation and blog instantly accessible to AI assistants like ChatGPT and Claude.

Every documentation and blog page now includes a "Copy page" dropdown that lets you:

• Copy the page as Markdown - Get clean, formatted Markdown optimized for LLMs

• Copy a shareable .md link - Direct link to the Markdown version

• Open in ChatGPT - Launch ChatGPT with the page pre-loaded

• Open in Claude - Launch Claude with the page pre-loaded

Why It Matters

When working with AI assistants, feeding them accurate documentation context is critical. Instead of copy-pasting HTML or having the AI scrape pages (which often loses structure), you can now give your AI assistant perfectly formatted documentation in one click.

Whether you're debugging an integration, exploring our APIs, or asking questions about DatoCMS features, your AI assistant now has direct access to our complete documentation in the format it works best with.

P.S. You can actually append .md to any page URL on our site to get its Markdown version — though we can't guarantee the quality of the conversion for all pages yet!

The DatoCMS JavaScript client is now fully type-safe. Records (the missing piece that wasn't) are also generated directly from your project’s schema.

This gives you real autocomplete and compile-time safety across your project.

The CLI bridges your schema and repo perfectly. Run a single command to generate types, and if your schema changes, rerun it to keep your code perfectly in sync.

$ npx datocms schema:generate schema.ts

The client also ships with new utilities to simplify record management, like duplicateBlockRecord(), inspectItem(), and mapBlocksInNonLocalizedFieldValue() to handle nested blocks, relations, and localized fields automatically.

Quick Links:

• CMA Client Package

• Configuring the CLI Docs

• Using the JS Client Docs

• Type-safe Development with TypeScript Docs

• Announcement post on the blog

You can now turn Structured Text fields back into Markdown with our new datocms/structured-text-to-markdown package. Perfect if you need clean Markdown output for your pipelines, exports, or tooling (or just a clean .md page for all the LLMs 🤭).

Just a lil

npm install datocms/structured-text-to-markdown

and you're set!

The renderer supports all DatoCMS Structured Text nodes and converts them to CommonMark-compatible Markdown:

Block Nodes

• Headings: # H1 through ###### H6

• Paragraphs: Plain text with double newlines

• Lists: Both unordered (-) and ordered (1.) lists with nested support

• Blockquotes: Lines prefixed with >

• Code blocks: Fenced code blocks with language support

• Thematic breaks: Horizontal rules (---)

Inline Formatting

• Strong: **bold**

• Emphasis: *italic*

• Code: `code`

• Strikethrough: ~~text~~

• Highlight: ==text== (extended Markdown)

• Underline: <u>text</u> (HTML fallback, no native Markdown)

Links

• Regular links: [text](url)

• Record links: Custom rendering via renderLinkToRecord

Full deets on the package and advanced usage are on the README.

We’ve fixed a long-standing issue with localized Link fields.

When editors used a Link field to reference entries, the dropdown showed records from all locales, even if those records were not available in the locale currently being edited. This often caused confusion in the UI, query errors and other unwanted production quirks.

Now, the Link field dropdown only shows records available in the current locale. This change should make managing localized content clearer and safer out of the box.

From now on, all API tokens — including the default non-editable tokens that are automatically created by DatoCMS — can be deleted.

Previously, default non-editable tokens (such as the read-only token) could not be removed. This change is a matter of security, giving you full control over your API tokens and allowing you to remove any unused or potentially exposed credentials.

💡 Reminder:
If you delete a default non-editable token generated automatically, it cannot be recreated. However, you can always create a new one with the same or custom permissions.

Many of you use shared Single Block fields to store common elements like title and image across models. Until now, these couldn’t be used as a model’s Presentation Title or Image — now you can!
You can now select a Single Block field in the Presentation tab, and DatoCMS will use the title and image set inside the chosen block as the model’s Presentation Title and Presentation Image.

How to use it

1. Go to Edit Model → Presentation tab

2. Select your Single Block field as Presentation Title or Presentation Image

3. Remember to set the presentation title and image you prefer in your Single Block’s own Presentation settings.

DatoCMS has long let editors organize records hierarchically. However, the feature was missing some elements to be considered as complete.

We covered the missing parts 💁‍♀️

• From today, a new "Tabular View" for trees of records is available - aside from the "Compact View", giving a bit more consistency on how records are visible across all model types. It brings all the freedom in playing with columns you know from the regular item list to hierarchically organized records too, without losing out on the drag-and-drop fun.

• We also removed the limitation to the number of records that can be organized in a tree: both the tabular and the compact view are now paginated, and records are incrementally shown as they are loaded.

To promote safer and more intentional permission management, new DatoCMS projects will no longer generate a default full-access API token (i.e. one with both read and write permissions for all APIs).

Previously, new projects came with two tokens by default: a full-access token and a read-only token. From now on, only the read-only token will be created automatically. This change encourages users to explicitly define the scope of each token based on their specific needs.

🔒 Reminder:
Existing projects still have this legacy token. If you’re using it, we strongly recommend ensuring it’s used only in trusted environments.