When working on a large project that scales many files, requires database interaction and requires milestone feature development it’s always good to have modules to make life easier. What exactly do I mean by a “module”? In C programming we would refer to it as a library but in web development we may simply call it a “module” - a bundle of cool functionality that stands on it’s own.

Stand-alone modules typically do have one dependency: a content management system or CMS. Many content management systems live and die by the ability to write your own plug-in modules. For instance, in the Drupal CMS we utilize modules for all forms of development, from custom additions to downloadable add-ons so we don’t go re-inventing the wheel.

Modules save time and energy and allow us to focus on new features and creative applications. We spent less time wondering how we’re going to create a forum system, an e-commerce system or a comment moderation system because someone has already done it and supplies it as a module for free or at a cost. You’ll be free to work on new features or extend those features created by others.

The concept of modular development isn’t in all content management systems or isn’t as solid and fully functional as major CMS solutions like Drupal. A developer relies on good application programming interface (API) documentation, ability to hook into core functionality through hooks/callbacks and a solid method to administrate your modules without ‘hacking’ core source files.

So, when choosing to work on the next big CMS look first at its supportability from a developer standpoint, documentation, forum support, feedback, and modular design. For example, another new CMS known as phpizabi has a nice support forum where developers can share ideas and talk with the community using the CMS.

We’re looking into Phpizabi for an upcoming website and we were happy to see it had modular development. As a designer, you want modular PHP projects because it means you don’t have to hire out developers to do the simple tasks; pay them for the hard ones. Phpizabi is building a “myspace” type CMS which can be extended way beyond that of a myspace clone. How? Their site breaks down a bullet list of features headed with:

Below is a list of some of the features found within PHPizabi, buts that’s not all; with additional modules, you can easily offer more then your garden variety site!

This allows a CMS to grow linearly with their development community. Many of their modules may cost you a few bucks to buy (to support the time and effort of the software engineers) but it’s well worth it when you count the hours it will take for you to code the same or the price to hire a developer on a per-hour basis (especially if they’ve never heard of Phpizabi).

Modules will help your site catch on just as a compiler will help an operating system grow in application space within the industry. Need proof? How about Phpizabi’s latest post:

Due to a sudden community peak which reflects in downloads, traffic and support requests, the PHPizabi support team has been receiving over hundreds of support tickets, mails and requests per day in the last two weeks. Even tho we are doing our best to fulfill every requests, the load caused by this literal flood have extended the support queue delay.

Is it catching on because it’s like myspace or because developers have taken an interest in extending its features? Maybe a bit of both, but definitely not just “buzz” - you need substance, contributors and a way for each contributor to interact together without stomping on each others feet; you need modules.