Editorial workflow, a real media library, and multichannel publishing, handled in core. When Drupal is right for a newsroom, and when it is not.
Editorial workflow and media management in core, JSON:API for multichannel delivery, accessibility built in, and a security model that survives a traffic spike when a story breaks.
Content moderation, draft and review states, scheduled publishing, and full revision history ship with Drupal. A large editorial team works without a single contributed module to vet or update.
The core Media Library treats images, video, and documents as entities you reuse across stories, not files glued to one post. For a deep archive that is the difference between findable and lost.
JSON:API is in core, so one editorial backend feeds the website, an app, partner syndication, or a headless front end without a second CMS or a sync job to babysit.
Drupal core ships WCAG 2.1 AA support: proper ARIA roles, keyboard navigation, and alt-text enforcement. Public broadcasters and university presses need that on the record, not as a promise.
A field-level permission model, mature caching, and a security team with a formal advisory process. When a story goes wide, the site stays up and the wrong people still cannot publish.
Four translation modules in core handle interface, content, and configuration. For a publisher serving several language editions, that is one less paid plugin in the critical path.
New media site, or a Drupal 7 newsroom that is now past end of life and overdue to move? We build the editorial workflow your team actually uses, wire up the media library and any second channel, and migrate your archive without breaking old URLs.
A small magazine that publishes a few articles a week and runs ads does not need Drupal's editorial machinery. WordPress on a managed host is faster to build and cheaper to run, and we build those too. Drupal earns its cost once you have a real editorial team, a large media archive, or a second publishing channel.
Adobe Commerce (formerly Magento) is the heavyweight of open-source ecommerce — built for B2B, multi-store, multi-warehouse retail at scale. Powerful but demanding: serious projects only, served by senior engineers.
A lean, free, MVC-architected ecommerce platform that runs on standard LAMP hosting. Strong fit for small-and-mid-business stores that need flexibility without Magento's overhead or Shopify's monthly tax.
WordPress powers 43% of websites worldwide — from solo blogs to enterprise corporate sites. We build, support, and customize WP projects from $99/mo.
Editorial scale and media handling. Drupal has content moderation, scheduled publishing, revision history, field-level permissions, and a reusable media library in core. WordPress can get there with plugins, but on a busy newsroom you are then maintaining and securing that plugin stack yourself. Past a real editorial team and a large archive, Drupal is the steadier base.
Yes. Its caching layers and CDN-friendly architecture are built for spikes, which is why broadcasters and national papers run on it. The work is in configuring the cache and host correctly, which is part of any build or migration we do.
Yes, through contributed modules and integrations with subscription platforms or a commerce layer. We scope the paywall to your model, whether metered, hard, or freemium, rather than forcing a one-size template, and we are honest that this is custom work rather than a checkbox.
Drupal 7 reached end of life in January 2025 and no longer receives security fixes, so staying put is a growing risk. The real decision is Drupal 10/11 versus leaving Drupal. We audit your modules and content model first, then give you a migration plan and an honest recommendation, even when it points away from Drupal.
That is one of its strengths. JSON:API is in core, so the same editorial backend can serve your website, an app, and partner feeds. We build headless when there is a genuine second channel and keep it monolithic when there is not, because decoupling doubles what you have to maintain.
A custom build or migration starts around $8,000 and runs higher with a large archive, a paywall, or multiple channels, over roughly 6 to 12 weeks. Ongoing maintenance is a separate fixed monthly retainer. We scope and price before any work starts.
Yes. We migrate articles, media, and authors, and we keep your old URLs working with redirects so you do not lose the search rankings the archive already earns. Losing URL history is the most expensive mistake in a publisher migration, and it is avoidable.
Drupal core targets WCAG 2.1 AA and Section 508, with accessibility treated as a project requirement rather than a plugin. We build on accessible themes and test against the standard you are held to, so the compliance claim is one you can actually back.
Newsrooms and publishers do not have a “blog” problem. They have a volume problem: hundreds of editors, thousands of assets, embargoes, syndication, and a homepage that has to survive a traffic spike when a story breaks. Drupal was built for exactly that shape of work, which is why The Economist, NBC, and a long list of public broadcasters run on it.
That does not mean Drupal is the right answer for every media site. A two-person magazine that publishes three posts a week does not need Drupal’s editorial machinery, and we will say so. This page is about the cases where it earns its keep.
The core argument is editorial workflow and media handling in core, not bolted on through plugins you have to vet and update yourself. Content moderation, scheduled publishing, revision history, and field-level permissions ship with Drupal. So does the Media Library, which treats images, video, and documents as reusable entities rather than file uploads stuck to one post.
For a real newsroom that combination matters more than the homepage design. An editor can hold a story in review, a sub-editor can publish it at 6am, and you can roll back a bad edit without a database restore.
Most publishers eventually push content somewhere beyond the website: an app, a partner feed, a smart-TV interface, an email platform. Drupal exposes everything through JSON:API in core, so a single editorial backend can feed a React or native front end without a second CMS. We build these headless when there is a genuine second channel, and we keep it monolithic when there is not, because a decoupled stack doubles the maintenance surface.
Drupal talent costs more than WordPress talent, and the build takes longer. If your site is essentially articles plus ads plus a newsletter signup, WordPress with a managed host will get you there faster and cheaper, and we build those too. Drupal starts to win past the point where you have a real editorial team, a large media archive, accessibility obligations, or more than one publishing channel.
The other common trigger is age. A lot of media sites are still on Drupal 7, which reached end of life in January 2025 and no longer gets security coverage. If that is you, the question is not whether to move but whether to move to Drupal 10/11 or off Drupal entirely, and that is a conversation worth having before the next vulnerability lands.
Run a mission-driven publisher or NGO newsroom? See how we build Drupal for nonprofits, with donations and CiviCRM.
The form below is pre-tagged: cms=drupal, site_type=media. CRM will know exactly which combination you came from.
