Blog

If you're evaluating CMS platforms for a compliance-sensitive organization, you've probably already ruled out the obvious stuff. You know you need proper permissions and workflow built in, not bolted on. You know your IT team is going to ask hard questions about hosting, patching, and long-term support. You know that a platform that looks good in a demo but falls apart under real security scrutiny isn't an option.

So now you're looking at Drupal and Concrete CMS, and you want someone to give you a straight answer.

AI is no longer a pilot program. It is not something your forward-thinking employees are quietly experimenting with on the side. It is embedded in daily work, whether your organization has formally adopted it or not. The question is not whether your team is using AI. The question is whether they are using it consistently, safely, and in ways that actually move the needle.

Everyone wants to "use AI." Few organizations are actually ready.

That's not a criticism. It's just reality.

Let me say the obvious thing first: this post was drafted with Claude. That makes it either a very transparent piece of content marketing or a funny coincidence, depending on how you look at it.

I used ChatGPT for most of my writing work for the past few years Outlines, first drafts, turning long posts into short ones. It works. But a week ago I switched to Claude as my main writing tool, and I want to explain why.

At some point, almost every website manager faces the same uncomfortable conversation: the current CMS isn't working anymore. Maybe it's held together with plugins from three different vendors. Maybe the editing experience is so painful that nobody on the team actually uses it. Maybe you've just outgrown it.

Whatever the reason, switching platforms means moving everything you've built (pages, images, metadata, documents, user permissions, the whole thing) to somewhere new without breaking what's working. That's content migration, and it's one of those projects that sounds straightforward until you're in the middle of it.

March 2026: Version 8 Is Done, Two Releases, and AI Gets Philosophical

Light news month, but there's some important stuff in here including a milestone we've been telegraphing for a while. Let's get into it.

This shouldn't come as a surprise to anyone who's been paying attention, but we want to be clear about it: as of this month, we are no longer providing security patches or releases for Concrete CMS version 8.

Nobody's debating whether AI belongs in the military anymore. That ship sailed. AI is already embedded in logistics systems, training simulations, intelligence analysis, and even service delivery platforms that help soldiers find out where to get their car inspected on base.

If you want to understand where AI is today, you don’t have to start in a research lab or a boardroom. Sometimes the clearest signals come from the internet itself.

Let’s get one thing out of the way.

AI is not going to “transform government overnight.”

It is not going to replace civil servants. It is not going to magically fix legacy systems. And it definitely is not a shortcut around governance.

Federal agencies are not looking for disruption. They are looking for reliability, compliance, and improved service delivery.

So instead of asking “How can AI transform everything?”, let’s ask a better question:

Where is AI already proving it can improve government websites safely?