Croogo, a simple CMS built on top of Cakephp. But for me, it has become my first building block for most cakephp application that I create. Why?
- It has the most common features setup already
- Less features, less complication
- It can be extended without touching the core CMS
Less features to reinvent
I hate reinventing the wheel over and over again. Those includes installing ACL (pain) and recreating commong login functionality such as login, create account, forgot password, reset password and account administration. Comments and captcha are also setup. Most of my apps almost always have these so croogo makes it really easy for me to not to worry about them.
Common features may be setup but it’s not too complicated nor too difficult to use it for your other goals. It is still cakephp and it follows the convention. Unlike other CMS made from cakephp, there aren’t a lot of features. I don’t use them all but I find less time coding by utilizing the features that is already setup in the CMS.
Another factor that makes croogo good as a building block is its plugin and hook system. I rebuilt the app that I created for a couple of months to croogo style in just a week. See their wiki to get a glimpse of what I’m talking about. Using the hooks, you can alter the behavior of the existing pages or features of the app. Using the plugins, you can enable or disable features. Think of wordpress and its plugin, it was built that way.
How to start?
In the next couple of articles, I’ll show you how to utilize the CMS to make you focus on your development to the real core. In the meantime, play around with it, read the wiki and join the google groups.