Wow, it’s been a while I guess. Been working too much as usual. And also, my PyroCMS Links Module is now available in the PyroCMS store. Yay!
So in my admittedly-limited free time I’ve been working on some PyroCMS-based projects and the more I work with it the more I love it. The main reason is that it’s built using Codeigniter which is a custom PHP framework. So if you know how to develop with CI you can easily get going with PyroCMS. And because it’s built on a custom framework, there’s a structure for customization.
By contrast if you’re developing with WordPress and you reach a point where you have to go beyond core and start building custom plugins there’s really no pattern to follow. Sure there are hooks and filters that allow you to customize as much as you want. But because WP is not a custom framework, it isn’t built for customization and there are no internal conventions for full-on custom modification. So each plugin you look at has a slightly different approach to accomplishing goals. The Pods CMS project attempts to create a standard for customization, but it has not yet been fully developed or fully adopted.
PyroCMS on the other hand, being CI based, strictly follows the MVC pattern and thus allows developers to anticipate the structure of any module, and replicate and override those modules if necessary. This is what custom frameworks setup to do. PyroCMS combines the code-base scalability with WordPress like features and the ability to quickly launch sites. Though, it still has a ways to go match up with WordPress on features.
This distinction is relevant for clients too. You decide to save on development costs and use a system like WordPress for your CMS. But then you start customizing everything and before you know it what you really have is a custom site attached to a WordPress install. This is fine until your developer goes on to bigger and better projects and you have to find a new one. Well, your WordPress install is too hacked and customized for average WordPress developers to handle. But because it wasn’t built on a custom framework, PHP developers will not be able to easily and quickly understand how the site was setup. Either way the cost of maintenance is going to be considerably higher than if you had gone custom in the first place.
Just a quick plug. I’m building my first project with PyroCMS. I was already a fan of Codeigniter, the core behind PyroCMS, but so far I’m impressed with just how easy it is to set up and extend CI with PryoCMS if you’re already familiar with CI and MVC. It lacks the community that WP has supporting it, so you’ll need to be prepared to do some custom code. But in a lot of cases it’s the ability to customize that you really need, but you don’t want to have to build a backend from scratch. PyroCMS seems to serve this purpose very effectively.