Joomla for publishers: built-in access control and multilingual tools

What is Joomla?

Joomla is a PHP content management system. Its repository describes it as a system that enables you to build websites and powerful online applications, distributed under the GNU General Public License version 2 or later. The copyright is held by Open Source Matters, Inc., which the README says was established in 2005.

Joomla sits between WordPress and Drupal in complexity. It ships several things as core components that other systems treat as add-ons, which is attractive if you want fewer third-party extensions to vet.

Our licence guide covers the GPL.

Who is Joomla best for?

It suits a publisher that wants multilingual capability, workflow and user management from the core install, and is willing to test them before committing. Associations, nonprofits and small organisations running a news section alongside static pages are a typical fit.

It is less natural if you want a thin writing-focused system. Compare WordPress for ease of hiring and Drupal for deeper content modelling.

A caution on method: docs.joomla.org refused our automated requests, so much of what follows comes from the official repository and the programmers manual rather than user documentation. Where we only saw that a component exists, we say so and do not describe how it behaves.

Editorial workflow

Joomla’s repository includes a Workflow component and a workflow plugin group, along with Users and Content History components. Those are the likely building blocks for stages, permissions and version history. A Scheduler component and a task plugin group exist for scheduled tasks.

We have not opened user documentation explaining how stages and transitions are configured or how revisions are restored, so we do not describe that process. If a formal approval chain matters, ask the Joomla manual or a developer to walk you through it on your intended version before committing. Our features checklist has the questions to ask.

SEO, structured data and feeds

The system plugin directory includes plugins for search-engine-friendly URLs (sef), redirects, HTTP headers, caching and schema.org structured data (schemaorg). The repository also has a Redirect component and a Finder component. We have not verified whether core publishes your own RSS output, so check that if you need it.

Because the schema.org plugin sits in core, structured data does not obviously depend on a third-party extension, unlike some other systems. We have not verified which schema types it outputs, and Google’s structured data documentation is the benchmark for what a news article needs. Sitemaps are not something we confirmed in the sources we could open.

Media, multilingual and performance

The repository has a Media component, Languages and Associations components, and a language filter system plugin. Taken together those are the pieces for sites in several languages with linked translations, built into the core package rather than added later. We did not verify the translation workflow itself.

For performance there is a cache system plugin and a Cache component. We make no claim about how they perform on a high-traffic site, and we did not open documentation on CDN use.

Hosting and requirements

For Joomla 6.x the manual recommends PHP 8.4, with 8.3.0 as the minimum. For databases it lists MySQL 8.4 (8.0.13 supported), MariaDB 12.0 (10.6 supported) and PostgreSQL 17.6 (14.0 supported). Web servers listed are Apache 2.4, Nginx 1.29 recommended (1.26 supported) and Microsoft IIS 10.

The manual labels 6.1 as Current, 6.2 as Upcoming, 5.4 as Legacy and 4.4 as Archived. Check which branch your site is on, and whether your host can run PHP 8.3 or later. The GitHub releases page marks 6.1.4 as a security release, so keep updates current.

Extending Joomla

Joomla’s plugin system is organised into groups: content, editors, finder, schemaorg, workflow, task, webservices, multifactor authentication and others. The manual says core extensions are those produced by Joomla and shipped with its installation packages. We did not verify the size of the third-party extension library, so we give no figure.

There is also a web services API. The repository’s api directory includes endpoints for content, categories, tags, fields, languages, media, menus and users among others. That makes a decoupled front end possible. See our headless guide for the trade-offs.

What Joomla costs

The licence is free. Cost sits in hosting that meets the PHP and database requirements, any paid extensions or templates, and developer time. We have not verified public prices for extensions, templates or hosts, so we give no figures. The cost guide lists categories.

Where Joomla falls short

• Much of the user documentation was not reachable to us, and we cannot vouch for how its workflow and multilingual features behave in practice.
• The sources we opened do not confirm built-in publication of your own RSS feed or XML sitemap.
• Major versions have defined support stages, and the manual already labels 5.4 as Legacy, so an older site faces upgrade work.
• We did not verify the size of its extension library or talent pool, so compare it with WordPress yourself.

A short trial plan for the unverified parts

Because we could not read the user documentation, the fastest way to close the gaps is a one-week trial on a staging copy of Joomla 6.1. Install it on a host that meets the PHP 8.3 minimum. Create a draft article, move it through the Workflow component’s stages, and confirm which user can publish it. Then add a second language through the Languages component, link two articles with the Associations component and check the language switcher on the front end.

Next, turn on the Schema.org plugin, publish a test article and inspect the structured data it produces against Google’s documentation. Finally, check whether your own RSS feed and XML sitemap exist or need an extension. Write down what you find. That record is worth more than any vendor feature list, including this profile.

The verdict for publishers

Joomla offers a lot in core: workflow, languages, associations, redirects, scheduled tasks, schema.org and an API. For a multilingual publication that wants fewer third-party extensions it deserves a real look, on the condition that you test the workflow and feed behaviour yourself.

For a pure blog or a developer-heavy structured content build, WordPress and Drupal are the usual comparisons. This profile rests on repository listings and the official manual, not an install of our own; see how we test.