One CMS to rule them all…?

The age old question, discussed by developers for years past…and for years to come. Is there one CMS to cater to the needs of any and all projects? CMS stands for Content Management System. This is an application, usually run on the web, that allows end-users to update the content of their website with ease. […]

The age old question, discussed by developers for years past…and for years to come.

Is there one CMS to cater to the needs of any and all projects?

CMS stands for Content Management System. This is an application, usually run on the web, that allows end-users to update the content of their website with ease. It can also allow content to be added en mass and worked with by the system (for example, an events guide that only displays upcoming events). For large websites with reams of content, a CMS is invaluable in the organisation, management and authoring of content. In the web industry of today, content management is becoming more and more important, as users with to have as much control over their websites as possible, while minimizing the time spent on the phone or emailing a web developer to update their website for them.

Various options present themselves when faced with the task of selecting a content management option. A variety of pre-made systems exist (WordPress, Expression Engine, Drupal, Joomla, Textpattern, etc) that have been tried, tested and extended by users worldwide. While many of these systems have limitations to their functionality and control from a development perspective, they have been tried, tested and are maintained by users worldwide, which is a huge advantage when developing a system that will grow and flow with the constant change that is the web.

Another option is building your own CMS. While this option is an incredible approach, allowing full control over functionality, integration of a design and extension of the core, it is difficult to keep up a custom CMS with a minimal developer count on the team constructing the system and potential security risks that may have been overlooked. While a these concerns are true, a custom CMS can also be as lightweight as desired, carry only the functionality necessary and be tailored to suit the needs of each website it is used for.

There are pro’s and con’s to each decision. What are your thoughts?

Enjoyed this article?

Get more insights on technical leadership, teams, and software development delivered to your inbox.