joomla-cms

Home of the Joomla! Content Management System

Automatically checked · GitHub checked 2026-11-13

joomla-cms

Before you switch

Evaluate hosting, migration and feature requirements before switching.

Overview

Joomla! CMS™

Build Status

ActionsPHPNodenpm
Build StatusPHPnode-ltsnpm

Overview

  • This is the source of Joomla! 6.x.
  • Joomla's Official website.
  • Joomla! 6.2 version history.
  • Detailed changes are in the changelog.
  • Release Managers responsible for Joomla! 6.2
    • Viviana Menzel @drmenzelit
    • Martin Kopp @MacJoom

What is Joomla?

  • Joomla! is a Content Management System (CMS) which enables you to build websites and powerful online applications.
  • It is a simple and powerful web server application which requires a server with PHP and either MySQL, MariaDB or PostgreSQL to run. You can find full technical requirements here.
  • Joomla! is free and Open Source software distributed under the GNU General Public License version 2 or later.

Looking for an installable package?

Joomla is not installable out of the box from this repository, please use:

How to get a working installation from the source

For detailed instructions please visit https://guide.joomla.org/user-manual/hosting/local-environment-setup

You will need:

Steps to setup the local environment:

  • Clone the repository:
git clone https://github.com/joomla/joomla-cms.git
  • Go to the joomla-cms folder:
cd joomla-cms
  • Go to the 6.2-dev branch:
git checkout 6.2-dev
  • Install all the needed composer packages:
composer install
  • Install all the needed npm packages:
npm ci

Things to be aware of when pulling: Joomla creates a cache of the namespaces of its extensions in JOOMLA_ROOT/administrator/cache/autoload_psr4.php. If extensions are created, deleted or removed in git then this file needs to be recreated. You can simply delete the file and it will be regenerated on the next call to Joomla.

Do you want to improve Joomla?

Which branch should my Pull Request target?

Using a simple classification keeps the project stable, transparent, and easy for everyone to contribute.

Type of changeWhat it meansTarget branch
Bug / Patch releaseThe change fixes an actual error. The software crashes, produces the wrong result, or behaves contrary to its specification. It can be resolved without large‑scale refactoring or new functionality.6.2-dev *
Feature / Minor releaseAnything that isn’t a strict bug – new behavior, refactoring, performance improvements, enhancements, UI tweaks, etc. These changes are bundled together for the next minor version.6.3-dev

* All bugs that already exist in version 5.4.x or 6.1.x or 6.2.x should be fixed in 6.2-dev.

A member of the maintainer or bug squad team confirms the classification and sets the appropriate labels when a PR is opened. If a PR is opened in the wrong branch, a maintainer will simply ask you to retarget it to the proper branch.

Copyright