In the previous two installments of this series we discussed the target audience for Joomla! 4 and beyond and the vision for the end user. In this third installment we’ll see things from the developers’ perspective, defining a vision for the PHP code’s architecture and design goals.
In the first post of this series we explored the unified marketing message for Joomla! 4 and beyond. Armed with this result let’s see how we can turn this into an actionable vision, starting with the improvements that affect our end users. The common theme behind all the improvements in this vision can be summed up as “Don’t make them think”.
Over the last year I’ve collected my thoughts on Joomla! the CMS, the project and the community. We’ve finally all come to the conclusion that Joomla! needs a revamp. The time is ripe to discuss the future. This is a very big subject so I’m going to present this as a series of blog posts. In this first installment we’ll talk about Joomla!’s target audience and a unified marketing message to frame our vision.
With the vote on the Joomla! restructuring coming to a conclusion pretty soon I would like to take a moment to reflect on what is the problem and how (or if) it’s being fixed.
As much as I love Joomla!, there is a shortcoming compared to the other two major Open Source PHP CMS, WordPress and Drupal: it doesn’t come with a command-line interface like wp-cli or drush. This is a bit of a problem when you’re in need of mass-provisioning sites with extensions or updates in an unattended manner. Using a CLI tool is the only way to provide a scriptable, efficient and unattended method of doing so. In this post we’ll see a practical way to overcome this limitation.
Hello, I’m Nicholas. Most of you know me as the author of popular components like Akeeba Backup and Admin Tools. Some of you know me as a frequent code contributor to Joomla!. I’m very outspoken to the point that people think I’m an asshole. Most likely I am. I was working as a business consultant long before I turned to full time software development and, as you know, business consultants are always seen as assholes, usually ranking lower in being well-liked than accounting and legal departments. But you know what else business consultants do besides being assholes? They know how to make an organisation do more with the same people (or even less, which is why people think we are assholes). So there you have it, I was refactoring businesses before I got to refactoring code. This is my take on refactoring Joomla!’s organisation structure. It’s a long read, ideal for a Sunday morning.
Two weeks ago we transferred our business site, AkeebaBackup.com, to a new host with a downtime of less than 15 minutes. The transfer of course took longer than that. Many people asked how we pulled this off. Keep reading on to find out!
I’m quite sure that most of you wouldn’t bat an eyelid on losing a pro bono job. You proposed to do some work for free, the other party didn’t agree for some odd reason, less work for you, end of story. But once in a while there’s a lesson to be had from such an experience, leading to interesting ripple effects. For example, a Joomla! guy ended up with a WordPress blog. Intrigued?
Joomla! 3.2 includes an abundance of new features appealing to end users and developers alike. One of these new features is two factor authentication. In this tutorial you will learn what two factor authentication is and how you can use it in your components to enhance the security of potentially dangerous or important operations, just like most banks do.
As a Joomla! developer I often find myself providing support to users of my software. Sometimes, despite my best intentions, I hit a stone wall: a server setting is amiss. In this case I explain to my users what the problem is and ask them to contact their host to rectify it. One of the most irritating situations I’ve found myself dealing with is when a host replies “we can’t do this for security reasons”. I would generally accept that, if only the host actually knew what they’re talking about. And, yes, I am specifically talking about the fopen URL wrappers and the fact that they are stupidly disabled on many hosts.