Drupal vs Joomla
Compare Drupal and Joomla by publishing scope, licensing, migration work and the operating responsibilities of a live site.
Which CMS model fits the publishing team?
Compare the content model and editorial tasks before choosing Drupal or Joomla. Both provide free open-source CMS software and need a hosting and maintenance arrangement. Drupal warrants a close look for structured relationships and modular application requirements; Joomla warrants a practical evaluation of article, menu, multilingual and access-control workflows. Validate the proposed implementation rather than inferring ease from the product name.
Seven differences that change the shortlist
| Buying question | Drupal | Joomla |
|---|---|---|
| Software model | Open-source modular CMS | Open-source website CMS |
| Content approach | Structured types and fields | Articles, categories and menus |
| Extension model | Modules and themes | Extensions and templates |
| Editorial review | Model the proposed workflow and permissions | Model user groups, access controls and publishing permissions |
| Languages | Validate language configuration against the content model | Core multilingual content associations |
| Free access | Free GPL software; hosting separate | Free GPL software; hosting separate |
| Ownership decision | Core, contributed modules and custom implementation | Core, extensions and template implementation |
Four worked buying briefs
These are hypothetical scenarios with explicit assumptions. They do not establish equal capabilities, measured usability or a negotiated price.
| Requirement | Evidence to collect | Acceptance condition |
|---|---|---|
| Content migration | A sample export and import covering references, media and languages | The approved sample preserves meaning and editable structure |
| Publishing control | A demonstration using the intended editor and reviewer permissions | Unauthorised changes cannot reach the live site |
| Delivery ownership | An architecture naming CMS, frontend, hosting and integration owners | Every production dependency has a support and recovery owner |
| Commercial scope | A quote for the required licence, capacity and operating services | The estimate includes renewal and implementation responsibilities |
Related content catalogue
How will one record connect to several pages?
Drupal: Model the record, fields and relationships before page templates.
Joomla: Demonstrate the article, field and extension design for the same records.
Count duplicate authoring tasks rather than judging the demo homepage.
Multilingual organisation
Can translators update a page without changing other languages?
Drupal: Test the proposed translation and moderation workflow.
Joomla: Test language associations and group permissions.
A translated interface does not establish a complete translation approval process.
Small editorial team
Can an occasional editor complete the weekly update?
Drupal: Prepare the intended editing form and required permissions.
Joomla: Prepare the intended article, menu and media workflow.
Use the same update task and record where training or customisation is required.
Long-lived website
Who maintains extensions over the project lifetime?
Drupal: Identify module support and custom code responsibilities.
Joomla: Identify extension and template support responsibilities.
Require an upgrade and recovery plan independent of the original developer.
Model the content before choosing templates
Select several real content examples: a service page, a staff profile, a policy document and a translated update. Record which fields are shared, which pages reference the same record and who may approve publication. The result is a content model that a supplier can implement and demonstrate.
A visually attractive template can hide duplicated content or awkward editing. Ask an editor to change a shared address once and inspect every page that uses it. If the proposal needs a third-party extension, put that dependency and its maintenance owner in the estimate.
Price the operating arrangement alongside the build
The absence of a core software licence does not decide the cheaper project. Migration, theme work, access configuration, extension support and operational monitoring all depend on the implementation. Compare a documented scope rather than two headline development quotes.
Request an upgrade rehearsal on a copy of the proposed site. The team should explain how it checks content, forms, permissions and integrations and how it reverses a failed update. Include that continuing work in the agreement with the host or maintenance partner.
Questions before you choose
Are Drupal and Joomla free hosted services?
Their core software is free and open source. Production hosting and maintenance are separate from the download.
Which is better for multilingual publishing?
Both deserve a task-based evaluation. Joomla documents multilingual associations in core; test each proposed language and approval workflow with actual content.
Should extension counts determine the choice?
No. Check whether the specific required extensions are compatible, maintained and supported for the proposed implementation.
Turn the comparison into your own evaluation
Use the same criteria and priorities for both products, keep unknowns unassessed and record the plan and evidence behind your ratings.
Build a Drupal vs Joomla scorecard →Keep the assumptions with the figures
Use the date, billing cycle, units and limits with each example. Check current account terms before purchasing. Unverified prices and model costs stay unpriced.
Download the buying examples as JSON ↓Share the comparison
Use these examples when discussing the shortlist with your team.