Pre-built vs Custom CMS
Utilising a pre-built, off the shield, content management system VS building your own is a never ending debate in web development circles. It seems that most people are strongly in favor of one or the other.
On August 18th, 2007, a "geek Olympics", called Full Code Press was held between a team from Australia and a team from New Zealand. The contest was simple enough: build a fully operation website and content management system. Oh, and they had 24 hours to do it!
Team Australia elected to use the powerful pre-built CMS, Drupal, for the competition. Team New Zealand, called CodeBlacks decided to build a custom CMS. It would first appear as a suicide mission to build a full blown custom CMS in just 24 hours when you can utilise the power and versatility of a pre-built system like Drupal.
Surprisingly, the CodeBlacks won! One of the members of the Australian team told Sitepoint that they spent a lot of time overriding the default styles that come with Drupal. Whereas the Codeblacks felt that the client required a solution that was very easy and simple to use, and that that would only be achieved by building a custom system.
I am a coder who does use pre-built systems like Drupal and Wordpress, but also likes to build custom systems. I think the solution chosen does come down to the exact requirements of the client. Using a pre-built system may well be quick and easy, but when you need to build something unique, it can very quickly become a time consuming mission to customise a pre-built system. Whereas if you build a custom solution from scratch, you can build it the right way for the client and the end solution will end up leaner, sleeker, faster and easier to use.
New comments for this tutorial have been turned off.