Drupal for publishers: structured content and a heavier build

What is Drupal?

Drupal is content management software that Drupal.org says is distributed under the GNU General Public License with no licensing fees. The Drupal Association is the non-profit that supports the project. The history page says Dries Buytaert decided to release the software behind drop.org in January 2001, so it is one of the older systems in this directory.

Drupal sits at the build-it-properly end of the spectrum. It is aimed at organisations with developers or an agency, and it is used where content has many types, many editors or many languages.

See the licence guide for what GPL means in practice.

Who is Drupal best for?

It suits a publisher that treats content as structured data: a magazine with distinct content types, several desks with different permissions, a news group publishing in several languages, or a site that feeds an app through an API. It also suits teams that want formal moderation states.

It is a poor match for a solo writer who wants a site live this week, or a team with no developer access. Compare WordPress for the simpler route, or Backdrop CMS for a lighter system with Drupal roots.

Editorial workflow

The Drupal User Guide has chapters on managing user accounts, with users, roles and permissions, and on setting up content structure, with taxonomy. The roles you define are yours to shape, so a desk-by-desk permission model is a configuration task rather than a plugin hunt.

The core Content Moderation module is the editorial piece. According to its documentation it adds workflows built from states such as Draft, Published and Archived and the transitions between them. A published version can stay live while a separate working copy is reviewed, and enabling the module creates a default Editorial workflow. You grant permissions to roles so authors can save drafts and editors can publish.

Scheduling is not part of that description. The contributed Scheduler module covers it: editors can schedule content, media, commerce products and taxonomy terms for publishing and unpublishing at set times. We have not verified how it interacts with moderation states, so test that combination.

SEO, structured data and feeds

This is where Drupal asks the most of you. Several SEO features come from contributed modules, each verified on its Drupal.org project page:

• Pathauto generates URL aliases for nodes, taxonomy terms and users from patterns. The project page reports 470,202 sites using it.
• Metatag provides page titles, canonical URLs, descriptions, Open Graph and Twitter Cards.
• Schema.org Metatag is a separate module for schema.org and JSON-LD, according to the Metatag page.
• Simple XML Sitemap produces sitemaps with hreflang and image support and supports IndexNow.

We did not verify RSS and feed behaviour in the pages we opened, so we make no claim about it here. Confirm it against your version before relying on it. The features checklist lists what to test.

Media, multilingual and performance

Multilingual is a strength. The User Guide says the base language of Drupal software is English and that the core Language module is required for any other language. Three further core modules handle different layers: Interface Translation for built-in text, Configuration Translation for things like field labels and site names, and Content Translation for the content itself. This is more granular than most systems, and more to configure.

We did not open documentation on core media handling, so we make no claim about it. For performance, the User Guide describes several cache types, including render and views caches, and ways to clear them from the admin interface or with Drush. Page and reverse-proxy caching strategy for a high-traffic news site is something to confirm with your developer or host.

Hosting and requirements

The 11.x branch of Drupal core requires PHP 8.3.0 or later in its composer.json. The requirements page lists MariaDB, MySQL, PostgreSQL and SQLite as database servers, says Drupal works on Apache, Nginx and other web servers, and recommends Linux or a similar operating system for hosting. Windows is supported only for development environments. Composer is needed for installation and updates.

That last point matters operationally. Updates are done through Composer, so whoever looks after the site needs command-line comfort. The releases page also shows Drupal 10.6.x receiving security support only until December 2026, so a site on an older branch has a deadline.

Extending Drupal

Drupal.org says the system extends through modules and themes. We did not verify a total count, so we give none. The Metatag, Pathauto, Scheduler and sitemap modules above show the pattern: core stays lean and contributed modules fill gaps.

For integrations, the JSON:API module is part of core. Its documentation describes it as an opinionated, zero-configuration way to allow RESTful create, read, update and delete operations on a site’s content, which suits a decoupled front end or an app. See our headless guide for the wider trade-offs.

What Drupal costs

The licence is free. The cost is in building and maintaining it: a developer or agency to model content types, configure moderation and roles, build the theme, install and test modules, and apply updates through Composer. We have not verified public prices for hosts or agencies, so we give no figures. See the cost guide.

Where Drupal falls short

• SEO and structured data depend on contributed modules, not core.
• Setup needs developer skill, including Composer.
• Scheduling is a contributed module, not a core feature, from what we opened.
• Older major branches reach end of security support on fixed dates, which creates upgrade work.
• Windows is supported only for development, so production hosting is expected to be Linux or similar.

What a sensible Drupal evaluation looks like

Scope a pilot around one desk. Ask your developer to model your main content types, enable Content Moderation with the Editorial workflow, and create roles for writer, sub-editor and publisher. Then add the contributed modules named above, Pathauto, Metatag, Schema.org Metatag and Simple XML Sitemap, and check their output against Google’s documentation.

Add Scheduler and test it with moderation states. Finally, ask what the update routine will be: who runs Composer updates, how quickly security releases are applied, and how the site will move from 11.x to 12 once it is stable. Those answers show whether you have the people to run Drupal, which matters more than any feature list.

The verdict for publishers

Drupal is the stronger tool when your publication has real structure: several content types, several roles with different rights, formal moderation, several languages or an API consumer. Core covers moderation, multilingual and JSON:API, and the contributed ecosystem covers SEO and scheduling.

For a small publication without developer time it is more machine than you need. WordPress will be quicker to launch, and Joomla sits in between. This profile is based on vendor documentation, not an install of our own; see how we test.