dotCMS

When was the last time a customer experienced your brand exactly the way you intended it?

Customers experience your brand as one thing. When the pieces don't connect, they feel it, even when they can't say why.

Integrated brand experience is not only about brand guidelines but also about the infrastructure that makes consistency enforceable: approval workflows, governed content, and a platform that does the policing so your team doesn't have to.

We wrote the guide that covers everything about brand experiences: https://www.dotcms.com/blog/guide-to-integrated-brand-experiences

At enterprise scale, asset chaos becomes a compliance risk.

Hundreds of teams. Multiple regions. Dozens of channels. Every piece of content needs to be approved, current, and traceable — before it goes anywhere.

Digital Asset Management gives compliance-led organizations a governed, centralized library where every asset is tagged, versioned, and distributed through controlled workflows. The right content reaches the right channel, every time.

Upload. Tag. Manage. Distribute. At any scale.

Read the full breakdown → dotcms.com/blog/what-is-digital-asset-management

Team dotCMS had a great day at the IDC CIO Summit in New York. This year's theme, the Rise of Agentic Systems, set the tone for every conversation on the floor. Proud to have sponsored, and even prouder to see our VP of Marketing, Inna Bosenko 🇺🇦, take the stage.

Inna opened with a stat IDC itself put on the table: by 2026, GenAI and automation will drive $1 trillion in global workforce productivity gains. Her question to the room - if agentic systems are the engine, which team should see those gains first?

Her answer: the Digital Experience team. The people building, managing, and marketing digital products now account for 18–25% of headcount and up to 30% of payroll in service-based industries. That makes them the single highest-leverage place for AI to land, but only if it lands in a way that doesn't dilute the brand, erode trust, or expose risk.

That's the bet we're making at dotCMS: AI-driven accessibility, brand governance, and personalization, built into a visual headless CMS that compliance-led organizations can actually trust at scale.

Thanks to IDC for a sharp, well-run event, and to every CIO who stopped by the booth!

🟣 New in dotCMS: Page Health.

Two scanners inside the Universal Visual Editor — Accessibility (WCAG 2.1 AA) + GEO (AI readiness score). Both catch what your CMS can't see, before publish.

Included. No extra cost.

Read more: dotcms.com/blog/compliance-and-discoverability-just-got-easier-in-dotcms

AI assistants are easy. AI agents are an architecture problem.

When an autonomous agent needs to publish across 40 sites, respect role-based permissions, and trigger the right workflow, most CMSs hit a wall.

Closed APIs. No machine-readable content models. No governance layer agents can call into.

That's the gap dotCMS is building for.

Read the full blog:

🔗https://www.dotcms.com/blog/from-ai-assisted-to-agent-ready-how-dotcms-is-building-for-the-agentic-age

May edition of dotDEV out now!

April was a plumbing month at dotCMS: visual UI for the Content Style Editor, sharper Content Editor refinements, image wrapping in the Block Editor, GraphQL responses that finally tell you what went wrong.

Inside this month:

🟣 A new 4-part headless series from our DevRel Afaq Javed (Zero to Launch, build a portfolio site with dotCMS + Next.js, end to end)

🟣Marc Boutillette on what "agent-ready" actually means at the architecture layer and why most "AI-ready" claims don't survive contact with an autonomous agent

Full issue in the article below.

https://www.linkedin.com/pulse/dotdev-may-edition-dotcms-7dubc

dotDEV: May Edition 01 · EDITORIAL From Jamie Mauro — Technical Writer, dotCMS Time flies; where does it all go? We lament its passage as though it signifies some loss. But time is precisely what we should ignore — indeed, forget entirely! When time slips by unnoticed, it means we have been living in those moments...

Headless doesn’t have to feel complicated.

In this tutorial, Afaq Javed, our Developer Relations lead, walks through how to set up a local dotCMS instance with Docker, clone the official Next.js headless starter kit, and connect your frontend using API tokens and environment variables.

By the end, you’ll have a working Next.js app powered by dotCMS, so content updates can happen in the CMS without hardcoding changes or redeploying your site.

🟣 Watch the full video: https://www.youtube.com/watch?v=kvfAWFSacS8&list=PL3Gqr5wygEszjb-ZMB3mcjkqb4-KfBXnk

Setting up the project (dotCMS + NextJs) | Part 01 🚀 Kick off your headless portfolio journey! In this video, Afaq Javed shows you how to set up a dotCMS instance locally using Docker, clone ...