# X to Drupal

> X to Drupal is the QED42 harness that modernises an existing website by replatforming it onto a real Drupal CMS. Modernising a website in 2026 means AI inside the CMS, digital sovereignty, an open architecture and readiness for AI agents, and the replatform is the step that gets a site there: the visual result preserved, the content model built the way a senior Drupal architect would model it, the delivered site wired for AI capabilities and LLM visibility, and the whole thing handed over so the content team can run it: a runbook generated in place of a training week, a Model Context Protocol connection that stages requested changes in the CMS as drafts, and the site's own brand captured as context. The result is an exportable Drupal CMS for any Drupal 11 host, with no vendor lock-in. The proof is qed42.com itself, migrated from Webflow to Drupal 11: 569 article bodies and 2,007 images moved across, zero custom modules, and the whole site installs as a Drupal Recipe. No parity percentage is published; the side-by-side comparison is the claim.

## About

- Site: https://x-to-drupal.qed42.com
- Maker: QED42 (https://www.qed42.com/)
- What it is for: modernising a finished website by moving it off a closed or limited platform onto Drupal 11, without redesigning it and without re-entering its content.
- Why teams do it: a real content model, AI capabilities configured in the CMS, search standing carried across, and an exportable site they own on any Drupal 11 host.
- Proven on qed42.com: Webflow to Drupal 11, 569 article bodies and 2,007 images moved across, zero custom modules, installs as a Recipe.
- Configured on delivery: Drupal's AI module suite against the client's own provider keys, generated media alternative text, per-bundle metadata generation, JSON-LD structured data, metadata, clean paths, redirects from old URLs, and sitemaps.
- Also configured on delivery: assistive authoring inside the editor, component preview before save, scheduled and bulk publishing, a trash area for deleted pages, editable enquiry forms with submissions kept in the site's own database, page and render caching with an object cache backend, WebP images cropped from a focal point, an enforcing content security policy with same-origin framing, HTTPS-only strict transport security carried over where the old site already sends it, on-site spam checks, a content editor role that is not an administrator role, required image alternative text, and provider keys read from the environment rather than stored in the database. An editorial approval workflow, with review before anything is published, can be added as part of a custom scope.
- Verified before handover: every address the old site advertises has a route on the new one, redirects included; content is traced unit by unit rather than sampled, with anything missing listed by name; and the result is checked again against the old site as it stands today.
- Handed over for the content team, not only for developers: a runbook generated as a phase of the run, holding the content architecture in plain English, every component shown as it looks populated, where each part of a page comes from and which component holds it, and how to manage taxonomies, menus and listings.
- Wired for a Model Context Protocol connection, an open standard that lets an AI assistant work through an application's own interface: a change described in plain language arrives in Drupal as a draft, built through the content type's own rules, with metadata, path and structured data filled as that content type already defines them, under the site's own roles and permissions. Nothing publishes itself.
- The design system and the voice of the existing site are captured as brand context and delivered with the site, so a change drafted a year later comes out in the client's own brand.
- Still in build, and labelled that way on the site: deeper AI authoring across an existing library, and a deeper automated SEO audit.
- Contact: business@qed42.com

## Pages

- [X to Drupal](https://x-to-drupal.qed42.com/): product page
- [What acceleration looks like](https://x-to-drupal.qed42.com/#acceleration): four typical site shapes (a brochure site, a marketing site, qed42.com and a publisher), each with its pages, page templates and forms, how many days the harness run takes, and how many weeks it is from kickoff to go-live. The harness run does the transcription work of a replatform, reading every page and recreating it on Drupal; the decisions, the review of the delivered site and the go-live window stay with people and set the pace around the run
- [Get in touch](https://x-to-drupal.qed42.com/#contact): the contact form, for what replatforming would mean for a specific site
- [What's included](https://x-to-drupal.qed42.com/included): what a replatform includes, and what is scoped separately
- [Blogs](https://x-to-drupal.qed42.com/blogs): the X to Drupal blogs

## Machine-readable copies

This site publishes its own prose in the formats an assistant can read directly, which is the same capability the delivered sites are meant to have.

- [Full text](https://x-to-drupal.qed42.com/llms-full.txt): every article inline, in series order, in one document
- Per-article markdown: append `.md` to any `/blogs/` URL

## Blog posts

Canonical source for the X to Drupal blog series. These URLs are the primary copies; any syndication points its canonical here.

- [Why replatform into Drupal and what X to Drupal provides](https://x-to-drupal.qed42.com/blogs/why-replatform-into-drupal-and-what-x-to-drupal-provides)
- [Fourteen generations of a website to Drupal system](https://x-to-drupal.qed42.com/blogs/fourteen-generations-of-a-website-to-drupal-system)
- [What building this taught us about working with AI](https://x-to-drupal.qed42.com/blogs/what-building-this-taught-us-about-working-with-ai)
- [We moved our own site from Webflow to Drupal](https://x-to-drupal.qed42.com/blogs/we-moved-our-own-site-from-webflow-to-drupal)
- [What your team gets when the site becomes a Drupal CMS](https://x-to-drupal.qed42.com/blogs/what-your-team-gets-when-the-site-becomes-a-drupal-cms)
- [What makes a Drupal site readable to LLMs](https://x-to-drupal.qed42.com/blogs/what-makes-a-drupal-site-readable-to-ai-search)
- [How we check a replatformed site really matches](https://x-to-drupal.qed42.com/blogs/how-we-check-a-replatformed-site-really-matches)