CERN Migrates home.cern Flagship Site to WordPress

I have spent twenty years arguing the same quiet point to enterprise clients: the value of a content management system is not what it can do on day one, it is what it can absorb on year ten. Redirections that outlive a re-org. Slugs that keep a decade of page rank intact. A plugin ecosystem mature enough that the integration you need at three in the morning already exists. A governance layer that scales when the org chart triples.

So when the institution that invented the web stands on stage in Krakow and says its flagship site is now served on WordPress, I take notice. Not because I needed the validation. Because the migration story behind that one sentence is the cleanest enterprise-WordPress case I have seen in years, and the people who keep asking me “but is WordPress really serious enough for our group” finally have something concrete to read.

This is the week to talk about it. The keynote landed at WordCamp Europe on Friday, the recap went up on Saturday, and the CERN side of the story has been in the open for over a year if you knew where to look. Here is what is actually in it, what it means for the rest of us, and what I would do with the news on a Monday morning.

What is actually new

WordCamp Europe 2026 ran at the ICE Krakow Congress Centre from June 4 to 6, with 2,458 ticket holders from 81 countries on site, per the official recap on WordPress.org. The opening keynote, “Two worlds collide: WordPress at CERN,” was delivered by Joachim Valdemar Yde, who has managed CERN’s web team since 2021, and Francisco Borges Aurindo Barros, who leads CERN’s WordPress infrastructure.

The line that made the room go quiet was Yde’s: “As of today, our main flagship website, home.cern, is now served on WordPress. It’s been automatically migrated, and it’s live.” That is verifiable in seconds. Open the page source on home.cern right now and you will see references to wp-content/themes/cern and wp-login.php. It is genuinely running on a custom WordPress theme.

The decision is not new. CERN’s web team announced the move from Drupal to WordPress in April 2025, after what they called “an extensive review of both Drupal and several other alternative systems.” The CERN Web Governance Board formally endorsed WordPress as “the foundation for CERN’s web presence in the years to come.” Drupal 10 reaches end of life in Q3/Q4 2026, so the timeline has a hard backstop.

The architecture is the part senior people will actually want to read. According to the keynote summary and the public CERN roadmap, the platform delivers a self-service portal where anyone at CERN can request a site in a few clicks. Behind it sits a shared distribution: a common theme plus a curated, security-hardened plugin set, with new sites provisioned on Kubernetes in roughly a minute. The first year of operation has set up hundreds of sites on this stack, with the goal of migrating 800+ websites in total. The migration is automated end to end — a single command lifts pages, headings and images and rebuilds them as Gutenberg blocks, with no downtime, and the team said they plan to open source the tool. The official CERN roadmap notes the phased rollout: WordPress Lite in October 2024, MVP in December 2024, Pilot in March 2025, general availability in May 2025, and automated Drupal migrations starting July 2025.

The early read on results, per Yde, has been overwhelmingly positive, with the easy wins coming in responsiveness and accessibility — exactly where heavy legacy Drupal installations tend to bleed.

Why it matters for WordPress and WooCommerce people

If you sell into legal, finance, healthcare, public sector or scientific research, the conversation just changed. “Is WordPress mature enough” was always a half-rhetorical objection — the answer was already “yes” if you knew the ecosystem — but you used to fight it with abstract arguments about market share. Now you can point at a particle physics laboratory whose web team chose WordPress after evaluating the field, whose governance board ratified the choice, and whose flagship site already runs on it. That is not a marketing slide. That is institutional procurement, in the open.

The architecture pattern is also worth copying. A single shared theme. A curated plugin set the security team has actually signed off on. Kubernetes provisioning so a new department site is not a project, it is a form. An automated content-to-blocks pipeline that does not stall on legacy markup. None of those pieces are exotic. We have shipped versions of each of them for clients in Istanbul and London. The novelty is treating them as one platform with one governance owner, instead of one bespoke build per stakeholder.

For agencies, the lesson is that the work that actually wins big migrations is no longer “build a beautiful theme.” It is governance, plugin curation, automated migration tooling, and the ability to explain a platform — not a site — to a procurement committee. The CMS layer, in this story, has become almost boring. That is the compliment.

What I would do (or not do) about it

If you have a Drupal client still on the fence, send them three links: the WCEU 2026 recap, the original CERN announcement, and home.cern itself. No commentary needed. The story does the work.

If you are scoping an enterprise WordPress build right now, stop pricing it as a theme project. Price it as a platform: shared distribution, plugin allow-list, Kubernetes or equivalent provisioning, an automated migration path, and a written governance charter that names who owns the plugin allow-list and how a new site gets approved. Those four things are what CERN actually built. Themes and design systems sit on top of them.

What I would not do is take this as a green light to rip out a working Drupal site that is delivering. CERN moved because Drupal 10’s end of life forced the question and because the maintenance burden of bespoke modules had grown faster than the team. Those are real reasons. “WordPress won at CERN” is not, on its own, a reason. If your Drupal site does not have either of those pressures, you can wait, plan, and pick the moment. And if you do decide to move, wait for CERN to open source their migration tool. They said they will. That tool is the part of this story most worth borrowing.

Twenty years in, the pattern keeps repeating: the boring layer — the part that handles redirections, revisions, slugs, governance, accessibility — quietly wins. This week, the institution that gave us the web agreed.