---
title: "Joomla: the community CMS born from the Mambo split"
description: "Joomla is born in 2005 as a fork of Mambo: MVC architecture in PHP, extension system, ACL and content management driven by the Open Source community."
url: "https://www.noze.it/en/insights/joomla-open-source/"
lang: "en"
alternate: "https://www.noze.it/insights/joomla-open-source/"
published: "2005-10-15"
author: "noze S.r.l."
keywords: "Open Source, Web, Joomla, CMS, PHP, Community"
---

# Joomla: the community CMS born from the Mambo split

Joomla is born in 2005 as a fork of Mambo: MVC architecture in PHP, extension system, ACL and content management driven by the Open Source community.

15 October 2005

## The split from Mambo

In 2005 the developer community behind **Mambo**, one of the most widely used Open Source CMSs, enters into conflict with **Miro**, the company that holds the trademark and governance. The dispute concerns control of the project: the foundation created by Miro limits the autonomy of volunteer developers. The core development team decides to leave Mambo and **fork** the source code. **Joomla** is born — its name derived from the Swahili word _jumla_, meaning “all together”.

The fork is not merely technical but above all organisational: from the outset, Joomla adopts a model of **community governance**, with decisions made collectively and transparency in processes. It is a direct response to the problem that caused the split.

## Architecture and content

Joomla is written in **PHP** and uses **MySQL** as its database. The architecture follows the **MVC** (Model-View-Controller) pattern, separating application logic from presentation. Content is organised into **articles**, grouped into **categories** and **sections**, with a **menu** system that defines site navigation.

The **template** system allows a complete separation of design from content structure: the site’s appearance can be changed without modifying the data. Templates use predefined **module positions** where dynamic content blocks can be inserted.

## Extensions and ACL

The **extension** architecture is the strength that positions Joomla between **WordPress** — oriented towards blogging and simplicity — and pure development frameworks. Extensions are divided into **components** (complete applications), **modules** (visual blocks), **plugins** (event interceptors) and **templates**. This taxonomy allows the CMS to be extended in a structured manner without modifying the core.

The **ACL** (Access Control List) system manages user permissions at a granular level: who can create content, who can publish it, who can administer specific sections. For sites with multiple editorial teams or complex editorial workflows, this functionality is essential.

## A middle ground

Joomla occupies a precise niche in the CMS ecosystem: more structured than WordPress for managing complex sites, yet more accessible than a development framework such as **Zend** or **Symfony**. The community is the engine of the project, producing documentation, extensions and translations in dozens of languages. For organisations that need an articulated portal without investing in custom development, Joomla represents a balance between flexibility and ease of use.

**Link**: [joomla.org](https://www.joomla.org)
