Your website isn’t broken because Joomla is hard. It’s broken because no one owns it. By "owns it," I don’t mean who signed the invoice. I mean someone capable, responsible, and empowered enough to actually make decisions before the whole thing rots.
There’s a lie many web agencies tell themselves: that clients choose them because they’re Joomla experts. That somehow their deep knowledge of Joomla is the deciding factor.
Twenty-six years ago, in the desert town of Swakopmund in Namibia, I jumped out of a plane without a parachute.
This is not a metaphor. It was a tandem skydive.
There is a persistent myth in open source that the biggest challenges are technical. People assume the problems lie in the code, the architecture, the governance model, or the roadmap. They’re wrong. One of the biggest problems facing open source software is the users.
You found a bug. Good. Now the real work starts.
Many developers think fixing a bug means making the error message disappear or getting the expected output to appear again. That is not fixing a bug. That is silencing a symptom. Real bug fixing requires understanding what changed, why it changed, and what that change affected.
If you are using Firefox and experiencing problems when editing content in Joomla — specifically where the TinyMCE editor keeps reloading, flashing, or constantly refreshing while typing — this article explains the solution.
There was a time when adding a tooltip, floating panel, or contextual menu meant reaching for a JavaScript library. Not anymore.
In this tutorial, you will learn how to create a template override for the Article view so that the intro text and full text are rendered separately. This makes it possible to apply different CSS styling to the intro section of an article.
If you use TinyMCE, the default editor in Joomla, you may have noticed a frustrating table issue.
