She dove into user.css . The new framework inside Cassiopeia was a revelation. She didn't need a heavy framework like Bootstrap 4. The template used modern, logical CSS variables. She changed --cassiopeia-color-primary to a deep burgundy, and the entire site shifted tone.
She installed a fresh copy of Joomla 4 on her local machine. The backend was cleaner, sharper. But she was nervous. In Joomla 3, she had lived in the template’s index.php , a chaotic but familiar workshop. She clicked .
Maya stared at the blinking cursor on her terminal. The email from the historical society wasn't rude, exactly, but it was firm: “The Thornfield Manor archive website is broken. Please fix. Also, make it look like this century.” joomla 4 templates
As the sun set, Maya loaded the new Thornfield Manor site. The Cassiopeia template, now dressed in burgundy and old gold, displayed the timeline flawlessly. The fonts were sharp. The images lazy-loaded without a plugin. The accessibility features—built into the template’s core—meant the site scored an A on her lighthouse test without her even trying.
And then she saw it.
The old site was a Joomla 3 relic—a maze of overrides, a Protostar template hacked beyond recognition, and CSS held together with duct tape and prayers. Maya sighed. She had been avoiding the upgrade to Joomla 4 for months. She’d heard the rumors: new media manager, new workflow, and a completely new template system called .
“Time to rip off the bandage,” she muttered. She dove into user
Two hours later, she hit a wall. The historical society wanted an interactive timeline of the manor’s fires (three major ones, 1789, 1842, and 1904). In the old days, she would have hacked a module position into the template’s index.php . But Joomla 4’s and TinyMCE 5 integration were smarter.