Quote:
|
I think that is actually no question of IF Content Management System or not, its a question of which CMS fits your clients needs best.
|
You seem to have missed my point, regardless of which 'off-the-shelf' CMS you use, they ALL suffer the same flaw; which is that they will need to be updated to avoid security flaws. In fact the more popular the CMS is (Wordpress, Drupal) the more likely it is that people will go looking for exploits. Even if it fits the clients needs perfectly, it doesn't help with this fundamental problem.
My question is how do you provide that as a service to the client. Do you leave them with a system that goes out of date, potentially dropping so far behind the current build it becomes irrepairable (not to mention vulnerable), or do you get them to pay you to keep it up to date?
I also can't see how using a prebuilt system like Drupal allows you to offer a more water tight service level agreement, unless I've misunderstood you? If the site fails on a grand scale, how does using someone elses code mean you can offer to support it? Unless you happen to know the Drupal code inside out and feel comfortable making repairs yourself, this seems impossible? (Not only that, but fixing flaws in someone elses code means you have just created a fork from the main build, yet more potential problems come upgrade time!)
Lets make it clear here I'm not talking about a small blog and a few static content pages... I need systems that can handle large numbers of users logging in and being served content in the form of audio and video on top of static content, calenders, forums and multiple blogs. Or as I like to call it 'the moon on a stick'.