Blog

We don't spend a lot of time patting ourselves on the back around here, but when TechRadar one of the largest technology publications in the world runs a piece calling Concrete CMS an "impressive, open-source solution" worth serious consideration, we'll take a moment to appreciate that.

Portland, OR — April 28, 2026 — PortlandLabs, the company behind Concrete CMS, announced today that Concrete CMS has received the Spring 2026 Leader Award from SourceForge, the world's largest B2B software review and comparison website. The award recognizes products that land in the top 5% of favorably reviewed software out of more than 100,000 listings based entirely on real user reviews.

May 4-7, 2026 : Do. Or do not. There is no try.

Three of our core team members (Myq, Korvin, and Andy) are clearing their calendars for four straight days to do nothing but fix bugs, harden security, and dial in the details for the next version of Concrete CMS. 

We're calling it Squash Week, and we want you there.

Let’s be honest, not every month is about big shiny releases. Some months are about lining things up so the next one actually matters. This is one of those months.

WordPress runs something like 43% of the web. That number gets cited constantly, usually as the end of the conversation. But market share is a funny thing to optimize for, it tells you what's popular, not what's right for your organization.

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.