In 2005, Joomla wasn’t launched with venture capital, a corporate roadmap, or even a clear long-term strategy. It began with something far more fragile and far more ambitious: a belief.
Open source does not work by accident. It works because people show up. We often describe that effort as "giving back." It’s a useful idea, but it may also be limiting how we think about contribution.
With Joomla 6.1, a small but powerful enhancement was added to the TinyMCE editor: dedicated buttons for inserting, editing and removing the HTML <abbr> element.
The 80/20 rule isn’t just some nice talking point for economics class. It’s real, it’s brutal, and it applies perfectly to software development.
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.
