IonizeCMS, a review
Hello! It's been a while since I last wrote on my website. Today I'm going to write you about IonizeCMS, a content management system based on CodeIgniter.
Well, I was hired by a web-services company and this is the main reason why I had little to no time, compared to before, for writing on my blogfolio. In these few months I even further expanded my skills, optimising what I learnt in the past years as self-taught developer. In this period I experienced with a particular CMS, the one that the company is currently using, i.e. IonizeCMS.
There are a couple of pros and cons about this CMS, let's see the PROs:
It's based on CodeIgniter. This means that anyone who has already developed on that framework is able to easily navigate through the code and the project structure.
It supports plugins ('modules'), and it's integration is really deep and structured.
It's natively multilanguage: never underestimate this thing!
It has a custom tags system which brings in the templates dynamic values (i.e.
<ion:theme_url />), with the possibility to nest them in order to create iterations etc (i.e. an articles iterator, medias iterator etc).
The back-end is really easy to use: the website is a series of collections of pages and articles; you have the possibility to create extended fields to pages, articles or medias, it has a decent media manager (which is in any case OK). When you become familiar with the potentialities of the system, you catch how powerful this CMS is.
Now the CONs:
It's not so famous and it's being developed by a close circle of developers: this means very little support, even if Michel-Ange Kunz will do the best to even reply you via email!
The tags system is both a pro and a con. It's good because it lets developers write themes on the fly (and it works for the most of the set-ups), but it becomes heavy when you have to do advanced content filtering. For this reason, I had to write some layouts in pure PHP, using the CMS classes (again, with no documentation). This is something the team is aware of, and they're already working on bringing the CMS classes on the layouts in an easier way.
What can I say? I'll always prefere this kind of CMS to Wordpress or Joomla, because it's essential and allows you to do whatever you like to do (even if you'll find less examples and you'll find harder to develop at the beginning).
Wordpress is, in my humble opinion, too much blog-oriented: you can of course create a non-blogging website with it, but the backend and the logics behind it will screech very loud. Also creating themes for it is just complicated and forces you to learn a lot of APIs before even start templating.
Joomla is based (always IMHO) on an old concept of web portal, and still continues its way. At this moment it's not a portal, it's not a blog system, it's... nothing and everything. It's API reaches an incredible amount of classes and they're constantly updated, forcing the developer a constant maintenance of his/her own plugins and scripts.
Of course these two CMSs are well-known and have plenty of plugins and shiny things, but they're too big to be maintained.
What's my feeling towards IonizeCMS? I think it kicks asses, still it kicks my own :P
- 2nd March 2014