Joomla shipped with Bootstrap 5.0

Bootstrap's integration into Joomla has been one of the most consequential architectural decisions in the CMS's history. In 2026, with Joomla 5.x firmly established and the Joomla 6.x series actively in development, that decision continues to pay dividends. This article traces the journey from Bootstrap 5.0's adoption in Joomla 4.0 through to the present day — examining what the framework shift meant at the time, how it reshaped the developer experience, and where Joomla's Bootstrap-powered front end stands today.

Joomla 4.0 launched in August 2021, shipping with Bootstrap 5.0 and marking a clean break from the jQuery-dependent, IE-burdened past. Joomla 5.x followed that trajectory, adopting Bootstrap 5.3 and delivering a more refined, accessible, and performant foundation. The community is now working toward Joomla 6.x, which promises to deepen those gains further — but the story really begins with the bold call to ship Bootstrap 5.0 when many CMS projects were still hedging.

TL:DR – Shipping with Bootstrap 5 was a turning point. It cleared out legacy debt, modernised the component library, and gave Joomla a credible front-end story heading into the mid-2020s.

Bootstrap

Bootstrap remains the dominant HTML, CSS, and JavaScript framework for building responsive, mobile-first web projects. Released under the MIT License, it has continued to mature steadily — Bootstrap 5.3 introduced native dark mode support, refined colour-system tokens, and expanded accessibility tooling, while keeping the migration path from earlier 5.x releases straightforward.

The framework's component library, grid system, and utilities API are now well-established reference points for Joomla template developers and third-party extension authors alike. Its comprehensive, actively maintained documentation means developers can get productive quickly without hunting for community workarounds.

Bootstrap GitHub — https://github.com/twbs

Joomla!

Joomla is a robust, free, open-source content management system distributed under the GNU General Public License version 2 or later. It powers everything from personal blogs to large-scale enterprise portals, backed by an active global community of developers, designers, and site builders.

Joomla 5.x is the current long-term support series, with Joomla 6.x in active development. Both series build on the Bootstrap 5 foundation established in Joomla 4.0, with each release refining the component integration, template architecture, and accessibility posture.

Joomla! GitHub — https://github.com/joomla/joomla-cms

What Was New in Bootstrap 5.0 — and Why It Mattered

Bootstrap 5.0 was not an incremental release. It represented a philosophical shift: drop the baggage, embrace modern standards, and trust that the web had moved on. For Joomla, adopting it at launch rather than waiting for a later point release was a deliberate signal to the developer community that the project was serious about keeping pace with the broader web ecosystem.

• No support for Internet Explorer — With Microsoft's formal end-of-support announcement in late 2020, dropping IE was both pragmatic and liberating. Developers could finally write CSS and JavaScript without defensive workarounds for a browser barely anyone was using.
• No dependency on jQuery — This was the headline change. Removing jQuery reduced bundle weight meaningfully, improved page load performance, and eliminated a significant source of version-conflict headaches across Joomla extensions.
• Rewritten JavaScript plugins — All interactive components were rewritten in vanilla ES6, improving code quality and making them easier to tree-shake and customise.
• Overhauled forms and buttons — Checkbox- and radio-powered button groups replaced the older JavaScript-toggle approach, producing more reliable and accessible interactive controls.
• CSS custom properties — Bootstrap began exposing more of its internals as CSS variables, opening the door to runtime theming without requiring a full Sass recompile.
• Utilities API — A programmatic system for generating utility classes gave developers a structured way to extend Bootstrap's helper layer rather than bolting on ad-hoc overrides.

The Lessons Joomla Carried into Bootstrap 5

Learning from the Bootstrap 3 Misstep

The Joomla community had been here before — and it had not gone well. When Joomla 3.0 shipped, it bundled a version of Bootstrap that was already ageing as Bootstrap 3.x arrived on the scene. The mismatch created years of friction: template developers working around stale components, extension authors maintaining parallel code paths, and users experiencing inconsistent interfaces depending on which third-party extensions they had installed. That experience shaped how the Joomla leadership approached the Bootstrap 5 decision, and the determination to ship a current version — and commit to tracking it — was a direct response to that earlier stumble.

Committing to Stability, Not Just Novelty

Adopting Bootstrap 5.0 at Joomla 4.0's launch could have been read as chasing the new and shiny. In practice, the project was careful to wait until Bootstrap 5 had a stable release rather than shipping a release candidate. The principle was straightforward: Joomla's own stability commitments meant it could not afford to anchor itself to beta-quality dependencies. That discipline has carried forward — Joomla 5.x ships with Bootstrap 5.3, a mature and well-supported point release, rather than racing to adopt any hypothetical Bootstrap 6 before it reaches production readiness.

Community Ownership of the Decision

The move to Bootstrap 5 was not handed down from a small core team in isolation. Discussions played out publicly on GitHub, in the Joomla Forum, and across community calls over an extended period. That transparency produced genuine buy-in: extension developers could plan their own migrations, template authors could begin testing early, and the broader community understood the rationale rather than simply absorbing a surprise breaking change. The contrast with some of Joomla's earlier major transitions was stark, and the smoother adoption curve reflected it.

Bootstrap 5.3 and the Joomla 5.x Generation

By the time Joomla 5.x landed, Bootstrap 5.3 had matured the framework considerably beyond its 5.0 roots. The most visible addition was a coherent dark mode system — not a simple colour inversion, but a properly designed set of colour tokens that allow templates to respond to the user's system preference or an explicit site-level toggle. For Joomla site builders, this meant that the Cassiopeia front-end template and any well-maintained third-party templates could offer dark mode without developers having to maintain a parallel stylesheet from scratch.

Bootstrap 5.3 also tightened the colour system more broadly, replacing hardcoded Sass variables with a layered token architecture that makes theming more predictable. Joomla's Cassiopeia template has been updated to take advantage of these tokens, and the documentation has been revised to walk template authors through the new approach. The result is a more composable theming model — developers can override a small set of high-level tokens and have those changes cascade consistently through components, rather than hunting down individual variable overrides.

The admin-side picture is more nuanced. The Atum administrator template remains visually distinctive and functional, but it carries a more complex dependency footprint that includes some older Joomla-specific UI patterns alongside Bootstrap components. Work is ongoing in the Joomla 6.x development cycle to bring Atum's component usage into closer alignment with Bootstrap 5.3 conventions — a process that requires care given how many third-party extensions rely on Atum's current markup structure.

Internet Explorer: Closed Chapter

In 2026, IE's absence from serious web development conversation is so complete that it barely warrants discussion — which is itself a measure of how much has changed. Microsoft retired Internet Explorer 11 in June 2022, and browser telemetry across the web has since reduced IE's share to levels that round to zero in most analytics dashboards. Joomla's early commitment to dropping IE support, made at a point when some stakeholders were still nervous about it, looks straightforwardly correct in retrospect. The practical benefit has been tangible: template and extension developers write CSS Grid, custom properties, and modern JavaScript without defensive fallbacks, and the resulting code is cleaner and easier to maintain.

Documentation, Templates, and the Developer Ecosystem

One of the quieter but more durable benefits of the Bootstrap 5 adoption has been the quality of the surrounding documentation. Because Bootstrap itself is extensively documented and widely taught, Joomla developers can draw on a large body of external learning resources — tutorials, component references, migration guides — rather than relying solely on Joomla-specific documentation. This has lowered the barrier to entry for developers coming to Joomla from other frameworks, and it has made it easier for existing Joomla developers to stay current as Bootstrap evolves.

The Cassiopeia template ships as Joomla's default front-end template and serves as the practical reference implementation for Bootstrap 5 usage within the CMS. Keeping it genuinely exemplary — rather than merely functional — matters because it sets the baseline expectation for third-party template authors. As Joomla 6.x development progresses, there is an opportunity to use Cassiopeia updates to demonstrate Bootstrap 5.3's more advanced capabilities, including the colour token system and the accessibility improvements introduced across the 5.x series.

Where Joomla Stands in 2026

The Bootstrap 5 adoption that felt like a calculated risk in 2021 reads, five years on, as a well-executed modernisation. Joomla 5.x is a stable, capable platform with a front-end foundation that is current, well-documented, and actively developed. The extension ecosystem has largely completed its migration away from jQuery dependencies, and the template market has embraced Bootstrap 5's theming model. The community's decision to move decisively rather than hedge has meant that Joomla developers are working with the same tools and conventions as the broader web development world, not a CMS-specific subset of them.

The work ahead — particularly with Atum modernisation and the continued evolution past Joomla 6.x — builds on that foundation rather than questioning it. The Bootstrap 5 bet has paid off, and the question now is not whether it was the right call, but how far Joomla can extend the gains it has already made.