We build on Joomla and we're obviously not neutral. So this comparison sticks to things you can check: what each CMS has in core, what needs a plugin, and what that means when an AI tool or an automation pipeline works with the site. Where WordPress is ahead, we say so.
The comparison
| Capability | Joomla 6 | WordPress |
|---|---|---|
| REST API in core | yes, since 4.0 (2021), JSON:API format | yes, since 4.7 (2016), WordPress's own JSON format |
| API authentication in core | per-user API tokens (Bearer) | application passwords (since 5.6), via Basic auth |
| Permissions | ACL per action, per category and per item, plus view levels | roles and capabilities, site-wide; per-category rules need plugins |
| Editorial workflow | configurable workflows with per-transition permissions, in core | draft / pending / published in core; custom workflows via plugins |
| Multilingual | core, with associations and hreflang | plugins (e.g. WPML, Polylang) |
| Structured data | schema.org plugins in core (since 5.0) | usually via an SEO plugin |
| Background jobs | Scheduler with task plugins; can run from real cron | WP-Cron, triggered by page visits unless replaced by real cron |
| CLI | cli/joomla.php in core | WP-CLI (separate project, very mature) |
| AI building blocks from the project | none in core yet | an AI team working on standard building blocks, including a way for plugins to expose "abilities" to AI tools and an MCP adapter |
| AI plugins available | a modest number | many more, in every category |
Where Joomla's core helps with AI work
Containment is built in
Letting an AI write to a CMS is mostly a permissions problem. In Joomla, the AI's account can be limited to "create drafts in these two categories, execute only the 'submit for review' transition", using core ACL and Workflows, enforced on every API request. In WordPress, a role like "Contributor" gets close, but restricting it to specific categories, or adding a review stage with its own permissions, means plugins. Each plugin is one more thing to trust and update.
One API style, documented by its routes
Joomla's API is JSON:API throughout: the same list/filter/paging conventions for articles, categories, users, menus and modules. For an AI tool or a generated client that's predictable. WordPress's API is more varied, partly because plugins add endpoints in their own style, but it's far more widely documented and used.
Multilingual and structured data without plugins
For AI translation pipelines, Joomla's core associations give a clear target: create the translated article as a draft, then associate it. Schema.org in core means AI-generated content gets structured data without another plugin in the chain.
Where WordPress is ahead
- Ecosystem. Far more AI plugins, integrations and tutorials. If you want an off-the-shelf AI feature today, WordPress probably has a plugin for it.
- Project-level AI work. The WordPress project has an AI team working on shared building blocks, so plugins can expose capabilities to AI tools in one standard way, including through MCP. Joomla has nothing comparable in core yet. Joomla integrations are built per site or per extension, on top of the API.
- Familiarity. More developers, and more AI-generated code that actually works, because models have seen far more WordPress code than Joomla code. In our experience, AI-written Joomla code needs more correction: older APIs, invented option names.
What this means in practice
- Content teams with review needs, multilingual sites, organisations with real permission structures: Joomla's core gives an AI integration a safer frame with fewer moving parts.
- Sites that want many ready-made AI features quickly: WordPress's ecosystem is hard to beat.
- Either way: the important parts are platform-independent. A dedicated user with minimal rights, drafts instead of publishing, model calls outside the page request, keys outside the database. Our Joomla versions of those are in Claude writes, Joomla publishes and where AI fits in Joomla's architecture.
Choosing a CMS for its AI story alone is a mistake. The AI tools change every few months, and the CMS stays for years. Choose for content model, permissions, languages and the team that will maintain it, then add AI on top through the API.