CMS / JOOMLA
Joomla: Complete Guide to the CMS, Articles, Templates, Extensions & Website Management
Joomla is an open-source content management system used to create and manage structured websites, digital content, navigation, users, extensions and controlled publishing workflows.
This guide covers Joomla’s own terminology and architecture accurately, with honest comparisons and no superiority claims.
- Articles, categories, menus, modules, components and plugins
- Templates, extensions, ACL and multilingual publishing
- SEO, security, performance, migration and maintenance
Component, modules, plugins and template are distinct roles. Understanding which is responsible for what makes Joomla far easier to work with.
THE BASICS
What Is Joomla?
Joomla is an open-source content management system for building and managing websites. It separates four concerns deliberately: the content you publish, the structure organising it, the presentation displaying it, and the functionality extending it — with a permissions system governing who can see and do what.
That separation is the defining characteristic. In Joomla, an article is a content item, a category organises it, a menu item determines how it is reached and displayed, a template controls how it looks, and modules and plugins add things around it. These are genuinely distinct layers rather than conveniences layered onto one another.
It is free and open source, released under the GPL. You install it on hosting you choose and control the site entirely. Joomla is maintained by a volunteer community and non-profit organisation rather than a commercial company — which shapes the ecosystem, the release cadence and the support model.
A note on terminology before going further: Joomla’s vocabulary is its own. A Joomla plugin is not a WordPress plugin. A Joomla component has no direct WordPress equivalent. Reading Joomla documentation with WordPress assumptions is the most common source of confusion for people arriving from elsewhere, and this guide uses Joomla’s terms as Joomla defines them.
Joomla in five parts
On versions: Joomla currently maintains 5.x and 6.x release series. Version numbers change frequently, so check joomla.org for what is current rather than relying on any article’s figures.
│
├── CONTENT
│ ├── Articles — individual content items
│ ├── Categories — hierarchical organisation
│ ├── Custom Fields — structured extra data
│ └── Media — images and files
│
├── STRUCTURE
│ ├── Menus
│ └── Menu Items — determine the view
│
├── PRESENTATION
│ ├── Templates
│ ├── Module Positions
│ └── Template Overrides
│
├── FUNCTIONALITY
│ ├── Components — main page functionality
│ ├── Modules — blocks in positions
│ └── Plugins — event-driven behaviour
│
├── USERS
│ ├── User Groups
│ ├── Access Levels — what can be seen
│ └── Permissions — what can be done
│
└── DATABASE & CONFIGURATION
ARCHITECTURE
How Joomla Works
When a page is requested, the web server hands it to PHP, which runs Joomla. Joomla reads the URL, works out which menu item applies, and that menu item determines which component produces the main content and how.
That last point is the piece that surprises people. In Joomla, the menu item is not just navigation — it defines a view. A menu item can be a single article, a category blog layout, a category list, featured articles, a contact form or a component view, each with its own display parameters. Navigation and content routing are the same system.
While the component builds the main content, modules render in positions the template defines, and plugins act at various points in the process — modifying content, handling authentication, adding behaviour. The template then wraps everything and controls presentation.
Everything structured lives in the database: articles, categories, menus, modules, users, permissions and configuration. Media files sit on disk, with the database recording references. That split matters for backups — a database backup without the media folder restores a site with every image missing.
Joomla runs on PHP and outputs HTML, CSS and JavaScript like any server-rendered application.
CONTENT
Articles, Categories and Menus
Articles are Joomla’s core content type. Each article carries its own content, publishing state, publish and expiry dates, author, access level, metadata and optional images. Articles can be marked featured, which makes them available to featured-article views.
Categories organise articles, and Joomla categories are genuinely hierarchical — a category can contain subcategories to multiple levels, each with its own settings and access level. Every article belongs to exactly one category. This is a real difference from CMS platforms where categorisation is a flat, many-to-many taxonomy, and it means your category tree is your content architecture rather than a labelling system.
Menus and menu items are where Joomla differs most from what people expect. A menu item determines what a URL displays and how. The common types include:
Single Article
Displays one specific article at its own URL.
Category Blog
Shows articles from a category in an intro-text layout.
Category List
Shows articles from a category as a compact list.
Featured Articles
Shows articles marked as featured across categories.
URL
Links to an internal or external address.
Component Views
Contact forms, search, news feeds and views from installed components.
A site can have several menus — a main navigation, a footer menu, a hidden menu holding items that exist only to define views without appearing anywhere. Modules can be assigned to display on specific menu items, which is how Joomla controls what appears where.
├── Home — Featured Articles
├── About — Single Article
├── Services — Category Blog
│ ├── Web Design — Category Blog
│ └── Development — Category Blog
├── News — Category List
└── Contact — Contact Form
Content Categories
└── Services
├── Web Design
│ ├── Article
│ └── Article
└── Development
└── Article
Illustrative structure. The menu defines views; the category tree organises content. They are related but separate.
One component produces the main content per page. Any number of modules fill the surrounding positions.
EXTENSIONS
Modules, Components, Plugins and Templates
These four terms are Joomla’s most important vocabulary, and mixing them up makes documentation impossible to follow.
A component provides major application functionality and produces the main content of a page. Exactly one component output appears per page, determined by the menu item. Core components handle articles, contacts, news feeds, search and site configuration; installed components add things like e-commerce, event management or directories.
Modules are blocks displayed in positions the template defines — a menu, a login form, latest articles, breadcrumbs, custom HTML, a search box, a language switcher. Modules appear around the component output, and each can be assigned to show on specific menu items. This assignment is how Joomla controls page-by-page layout without separate templates.
Plugins are event-driven. They run when Joomla triggers specific events — before content is displayed, during authentication, when a form is submitted, at system initialisation. They typically have no visible output of their own; they modify behaviour. This is genuinely different from a WordPress plugin, which is a general-purpose extension container.
Templates control presentation: layout, typography, colours, responsive behaviour and which module positions exist. Joomla uses separate templates for the site frontend and the administrator backend. Template overrides let you change how a component or module renders without editing its files — your changes survive updates, which is the mechanism to use rather than modifying extensions directly.
Extensions is the umbrella term covering all of these plus languages. When Joomla documentation says “extension”, it means the category, not a specific type.
MANAGEMENT
The Administrator, Media and Custom Fields
Joomla separates the site from the administrator, reached at a distinct URL with its own template. The administrator covers Content (articles, categories, featured, media), Menus, Components, Extensions (manage, install, modules, plugins, templates, languages), Users and System (configuration, cache, updates, permissions).
System is worth knowing well — global configuration, SEO settings, cache control, update management and global permissions all live there, and it is where most site-wide behaviour is set.
Media management handles images and files in a folder structure you control. Two habits help: organise into meaningful folders from the start rather than accumulating everything in one place, and name files descriptively before uploading. Image dimensions, compression and alt text matter for both accessibility and image SEO.
Custom fields are one of Joomla’s more useful features and are frequently underused. They let you attach structured data to articles, contacts and users — a product specification, an event date, an author biography, a location. Instead of embedding that information in free-form article text where it cannot be queried or styled consistently, it becomes a defined field with its own type, validation and display.
Fields can be grouped, assigned to specific categories, and given their own access levels. For any content type with repeatable structured information, this is considerably more maintainable than formatting it by hand each time.
Custom field examples
- Product specifications on catalogue articles
- Event date, time and venue
- Author credentials on editorial content
- Location details on branch pages
- Downloadable file attachments
- Structured contact information
Joomla's default groups. They are a starting point, not a fixed structure — groups can be renamed, nested and created to match how an organisation actually works.
ACCESS CONTROL
Users, Groups and Joomla ACL
Joomla’s access control list is one of its more distinctive features, and it separates two questions most systems combine.
Access levels control what a user can see. Every article, category, menu item and module has an access level, and users see only what their groups permit. This is how you build content visible to members but not the public, or an internal section for staff.
Permissions control what a user can do — create, edit, edit own, publish, delete, access the administrator, manage extensions. These are set globally and can be overridden per component, per category and per article, inheriting down the tree unless explicitly changed.
The combination allows genuinely granular arrangements: a group that can edit articles in one category but only view another, publish their own work but not others’, and never reach the extension manager. Organisations with editorial workflows and multiple content owners tend to find this valuable.
Two honest caveats. The inheritance model takes time to understand, and permission problems in Joomla are usually inheritance problems — a setting applied at a level you have forgotten about. And this flexibility is only an advantage if you need it; a small site with two editors does not benefit from a permission architecture designed for a newsroom.
The default groups shown alongside are a starting point. They can be renamed, nested and extended — treating them as a fixed hierarchy misses the point of the system.
SEO
Joomla SEO
Joomla does not make a site rank, and neither does any CMS. What it provides is control over the things that matter, which is a reasonable starting position and nothing more.
Search Engine Friendly URLs are the first setting to address, in Global Configuration. They turn Joomla’s internal query-string URLs into readable paths. URL Rewriting goes further by removing the index.php segment, but it requires the corresponding server configuration to be in place — enabling it without that produces a site of broken links, which is worth knowing before you flip the switch.
URLs derive from menu item aliases and the menu structure, which is why menu architecture and URL architecture are the same decision in Joomla. Plan it before publishing, because changing it later means setting up redirects for everything.
One Joomla-specific issue worth watching: the same article can be reachable through several paths if it appears in multiple menu items or category views. That produces duplicate URLs, and it is worth reviewing your menu structure with this in mind. See our technical SEO guide.
Metadata can be set per article and per menu item, with the menu item generally taking precedence for the page. Sitemaps, structured data and redirect management are typically handled by extensions, since core coverage of these is limited.
Joomla SEO checklist
- Search Engine Friendly URLs enabled in Global Configuration
- URL Rewriting configured with the matching server rules
- Menu item metadata completed for key pages
- Article metadata reviewed where it matters
- One H1 per page, with a logical heading structure
- Descriptive, readable menu item aliases
- Internal links added within article content
- XML sitemap generated by a suitable extension
- Redirects configured for any changed URLs
- Images sized, compressed and given alt text
- Structured data added where genuinely applicable
- Duplicate access paths to the same content reviewed
[ ] Search Engine Friendly URLs enabled in Global Configuration [ ] URL Rewriting configured with the matching server rules [ ] Menu item metadata completed for key pages [ ] Article metadata reviewed where it matters [ ] One H1 per page, with a logical heading structure [ ] Descriptive, readable menu item aliases [ ] Internal links added within article content [ ] XML sitemap generated by a suitable extension [ ] Redirects configured for any changed URLs [ ] Images sized, compressed and given alt text [ ] Structured data added where genuinely applicable [ ] Duplicate access paths to the same content reviewed
Security practices
- Keep Joomla core updated promptly
- Keep every extension updated
- Install extensions only from reputable sources
- Remove unused extensions rather than disabling them
- Use strong credentials and two-factor authentication
- Restrict Super User accounts to those who need them
- Serve the whole site over HTTPS
- Keep tested, off-site backups
- Apply least-privilege permissions
- Follow Joomla security advisories
- Test updates on staging first
- Keep the server and PHP version supported
Performance workflow
[ ] Keep Joomla core updated promptly [ ] Keep every extension updated [ ] Install extensions only from reputable sources [ ] Remove unused extensions rather than disabling them [ ] Use strong credentials and two-factor authentication [ ] Restrict Super User accounts to those who need them [ ] Serve the whole site over HTTPS [ ] Keep tested, off-site backups [ ] Apply least-privilege permissions [ ] Follow Joomla security advisories [ ] Test updates on staging first [ ] Keep the server and PHP version supported
SECURITY & PERFORMANCE
Security, Performance and Hosting
No CMS is secure by itself, and Joomla is no exception. Security depends on the whole stack: core version, extension quality, credentials, permissions, server configuration and hosting.
The dominant risk is the same across every CMS: outdated software and third-party extensions. Most compromises exploit known vulnerabilities that were patched, sometimes long before. Joomla publishes security advisories, and following them is more valuable than any security extension.
Extension selection matters here. Before installing, check whether it is actively maintained, when it was last updated, whether it supports your Joomla version, and whether the developer has a record of responding to issues. An abandoned extension is a liability that gets worse with time.
For performance: hosting sets the floor, and Joomla’s built-in caching (conservative and progressive page caching, plus the system cache plugin) reduces repeated work. Beyond that, the usual factors apply — image optimisation, reducing extension overhead, compression, a CDN where the audience is spread out, and database maintenance as the site grows.
Extensions are the variable most people underestimate. Each one may add queries, CSS and JavaScript to every page. Measure rather than guessing — see Core Web Vitals and website speed.
For hosting, Joomla needs a supported PHP version, a supported database (MySQL, MariaDB or PostgreSQL) and HTTPS. Joomla’s documentation publishes current technical requirements — check joomla.org rather than trusting figures in any article, since they change with each release series. See our hosting guides.
DEVELOPMENT
Development, APIs, Multilingual and Accessibility
Joomla development uses PHP on the server with HTML, CSS and JavaScript in the browser. Developers can build components, modules, plugins and templates, and Joomla provides a framework and APIs for interacting with content, users, the database and the event system.
Template overrides are the technique worth learning first. They let you change how a component or module renders by placing a modified file in your template’s html directory, without touching the extension itself. Your changes survive extension updates — which is exactly the problem that editing files directly creates.
Plugins hook into Joomla’s event system, running code when specific events fire. This is how you add behaviour without modifying anything else.
Joomla includes a Web Services API for interacting with site data over HTTP, supporting integrations, headless use and external applications. Check current Joomla documentation for available endpoints and authentication rather than assuming from other platforms.
Multilingual support is built into Joomla core rather than requiring an extension, which is genuinely notable. You install language packs, create content languages, assign language to articles and menu items, associate translations with each other, and add a language switcher module. It takes deliberate setup — several steps in a specific order — but it is native functionality.
Accessibility depends on your template, extensions and content rather than on Joomla itself. Semantic headings, keyboard navigation, contrast, alt text, form labels and visible focus are implementation responsibilities. See our website accessibility guide.
Joomla includes workflow functionality for content, allowing defined publishing stages with transitions between them. Combined with ACL, this supports organisations where content genuinely needs approval before publication rather than relying on convention.
Multilingual setup order
- Install language packs
- Enable the language filter plugin
- Create content languages
- Assign language to categories and articles
- Create a menu per language
- Associate translated items with each other
- Add a language switcher module
COMPARISONS
Joomla Compared With Other Platforms
Each of these makes different trade-offs. None is better in general — which suits a project depends on the content, the team and the requirements. What follows describes differences rather than declaring winners.
Joomla vs WordPress
The clearest difference is the content model. Joomla’s single hierarchical category tree is more structured; WordPress’s flat taxonomies are more flexible. Which is an advantage depends entirely on whether your content has genuine hierarchy. See our WordPress guide.
Joomla vs Drupal
Both handle structured content and granular permissions. Drupal starts closer to a framework and expects more configuration; Joomla arrives closer to a working site. See our Drupal guide.
Joomla vs website builders
Compared with Webflow, Wix or Squarespace, the trade is control against convenience. Self-hosting means responsibility for updates, backups and security, and freedom to do anything the platform would restrict.
Joomla vs WordPress with Elementor
This comparison needs care, because the things being compared are not equivalent. Joomla is a CMS with its own architecture. Elementor is a third-party visual page builder plugin for WordPress — not part of WordPress Core, and not a CMS in its own right.
The realistic comparison is Joomla against WordPress-plus-Elementor as a combination. Elementor offers visual page design with extensive layout control, at the cost of another dependency and its own CSS and JavaScript. Joomla’s equivalent territory is templates, module positions and overrides — more structural, less visual, and requiring more comfort with how the system fits together.
Someone wanting to design pages by dragging elements will find WordPress with Elementor closer to that. Someone wanting a defined content architecture with granular permissions will find Joomla closer to that. They are answering different questions.
FIT
When Can Joomla Be a Good Fit?
Joomla can be considered when a project’s shape matches what it does well. That framing is deliberate — no CMS is the right answer for every project, and the honest question is fit rather than ranking.
Structured Content
Where content has genuine hierarchy that a category tree models well.
Granular Permissions
Where different groups need genuinely different access to see and do things.
Multilingual Requirements
Where multiple languages are needed and core support is preferable to a plugin.
Editorial Workflows
Where content genuinely needs review and approval before publication.
Technical Teams
Where there is capacity to learn the architecture and maintain the site properly.
Full Control
Where self-hosting, data ownership and portability matter.
Equally worth stating: Joomla is a weaker fit where a project needs the largest possible ecosystem of ready-made extensions, where nobody has capacity to learn the architecture, or where a simple brochure site would be served faster by something less structured. Choosing a CMS because it is powerful, then using none of that power, is a cost with no return.
Business Websites
Service pages, structured content and contact functionality.
News & Content Portals
Category hierarchies, editorial workflows and multiple authors.
Community Sites
User accounts, groups and access-controlled content.
Membership Sites
Content restricted by access level to registered groups.
Educational Sites
Structured course and resource content with role-based access.
Organisation Sites
Multilingual requirements and defined publishing processes.
Multilingual Sites
Using core language features rather than extensions.
E-Commerce
Through suitable commerce extensions rather than core functionality.
OPERATIONS
Migration, Maintenance and Troubleshooting
Migration covers two different scenarios worth separating. Moving a Joomla site between hosts or domains is relatively mechanical: back up, move files and database, update configuration, test, switch DNS, monitor. Migrating between Joomla version series is a different exercise, since extension compatibility becomes the limiting factor — and migrating from another CMS is different again, involving content mapping and URL redirection.
In every case the order is the same: back up first, audit what you have, check extension compatibility, work on staging, test thoroughly, map redirects for any URL changes, then launch and monitor. Do not assume a version upgrade path that worked on one site applies to another with different extensions.
Troubleshooting in Joomla has one reliable starting question: what changed? Problems almost always follow an update, a new extension or a configuration change.
These are possible causes, not diagnoses. The same symptom can have several causes, which is why isolating changes on staging beats applying fixes found online.
Maintenance checklist
- Joomla core updated
- Extensions updated
- Backups running and verified by restoring
- Security advisories reviewed
- Performance measured
- Broken links checked
- Forms tested end to end
- User accounts and permissions reviewed
- Unused extensions removed
- Database reviewed as it grows
- Search Console checked
- SSL certificate and domain current
- Major changes tested on staging
[ ] Joomla core updated [ ] Extensions updated [ ] Backups running and verified by restoring [ ] Security advisories reviewed [ ] Performance measured [ ] Broken links checked [ ] Forms tested end to end [ ] User accounts and permissions reviewed [ ] Unused extensions removed [ ] Database reviewed as it grows [ ] Search Console checked [ ] SSL certificate and domain current [ ] Major changes tested on staging
REFERENCE
Joomla Core Concepts at a Glance
Joomla’s vocabulary is precise, and using it correctly makes documentation, forums and extension descriptions far easier to follow.
Keep Core Updated
Security releases are the highest-value maintenance you do.
Vet Extensions
Check maintenance status and version support before installing.
Test Backups
A backup never restored is a hope, not a backup.
Use Staging
Test updates and changes before they reach visitors.
Plan Structure First
Category tree and menus decide your URLs.
Use Overrides
Never edit extension files directly.
Remove Unused Extensions
Disabled code still sits on the server.
Review Permissions
Least privilege, checked periodically.
Measure Performance
Diagnose before optimising.
FAQ
Joomla: Frequently Asked Questions
Short answers to the questions people ask most about Joomla as a CMS, platform and development environment.
NEXT TOPICS
Related CMS Topics
Each platform trades control, ease of use, hosting responsibility and cost differently. Which suits a project depends on the project.
WordPress
A widely used open-source CMS with a larger ecosystem and a flatter content model.
Drupal
An open-source CMS oriented toward structured content and complex requirements, with a steeper learning curve.
Webflow
A hosted visual development platform combining design tools with a CMS.
Wix
A hosted builder focused on ease of use, with infrastructure managed for you.
Shopify
A hosted commerce platform built specifically for selling online.
Squarespace
A hosted builder with design templates and integrated hosting.
Framer
A design-led site builder with a visual canvas and publishing.
Website SEO
How SEO principles apply across any CMS, including Joomla.
Explore the CMS Landscape
Continue exploring CMS platforms, hosting, website development, SEO, performance and ecommerce topics.