Comments on: To CMS or not to CMS? http://maymay.net/blog/2005/12/24/to-cms-or-not-to-cms/ The brutally honest, first-person account of Meitar Moscovitz's life. Wed, 07 Jan 2009 17:10:16 +0000 http://wordpress.org/?v=2.7 hourly 1 By: Meitar http://maymay.net/blog/2005/12/24/to-cms-or-not-to-cms/comment-page-1/#comment-9370 Meitar Sun, 25 Dec 2005 15:36:36 +0000 /?p=87#comment-9370 Those are really good points, Gunnar, I must admit that it's been a short while since I took a serious look at Drupal. Nevertheless, even with a system like Drupal in place, it will fail unless the organization using it can, in fact, use it in a manner that works for them. Most of what I was trying to talk about was actually how people organize their own non-technically dependant workflows rather than which software they use for the web. Perhaps it's time I take a closer look at Drupal, though. Thanks for the comment! Those are really good points, Gunnar, I must admit that it’s been a short while since I took a serious look at Drupal.

Nevertheless, even with a system like Drupal in place, it will fail unless the organization using it can, in fact, use it in a manner that works for them. Most of what I was trying to talk about was actually how people organize their own non-technically dependant workflows rather than which software they use for the web.

Perhaps it’s time I take a closer look at Drupal, though. Thanks for the comment!

]]> By: Gunnar Langemark http://maymay.net/blog/2005/12/24/to-cms-or-not-to-cms/comment-page-1/#comment-9343 Gunnar Langemark Sun, 25 Dec 2005 08:46:41 +0000 /?p=87#comment-9343 Don't compare a relatively primitive CMS like PostNuke to an Application Development Platform like Drupal, which will support advanced community solutions, advanced taxonomy based solutions etc. Drupal is based on a philosophy and an architecture which will enable you to do things that systems like PostNuke and Wordpress can only dream of. Drupal is way too advanced to do just a simple company brochure site. You can disable complex functionality and build a simple site, and then enable it when the client wants it - if ever. You cannot do that with a Wordpress or a Postnuke system which will stay primitive forever - unless you want to lift all the content to another solution and start all over. Jeffrey Veen is right that most small solution will never become advanced, and that the "small, slim solution" is a better bet. But if you're an internet consultant and not a designer, you would like your clients to dig further into e-commerce which means more advanced solutions. So I'd go for the scaled down Drupal as a starting point. Don’t compare a relatively primitive CMS like PostNuke to an Application Development Platform like Drupal, which will support advanced community solutions, advanced taxonomy based solutions etc. Drupal is based on a philosophy and an architecture which will enable you to do things that systems like PostNuke and Wordpress can only dream of.
Drupal is way too advanced to do just a simple company brochure site. You can disable complex functionality and build a simple site, and then enable it when the client wants it - if ever.
You cannot do that with a Wordpress or a Postnuke system which will stay primitive forever - unless you want to lift all the content to another solution and start all over.
Jeffrey Veen is right that most small solution will never become advanced, and that the “small, slim solution” is a better bet. But if you’re an internet consultant and not a designer, you would like your clients to dig further into e-commerce which means more advanced solutions.
So I’d go for the scaled down Drupal as a starting point.

]]>