Comments on: Content Management Systems Reconsidered http://www.andrewlih.com/blog/2009/02/24/content-management-systems-reconsidered/?utm_source=rss&utm_medium=rss&utm_campaign=content-management-systems-reconsidered USC professor and author of The Wikipedia Revolution Mon, 30 Jan 2012 17:18:19 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Amelie Hooley http://www.andrewlih.com/blog/2009/02/24/content-management-systems-reconsidered/comment-page-1/#comment-460513 Amelie Hooley Sat, 29 Oct 2011 23:16:46 +0000 http://www.andrewlih.com/blog/?p=336#comment-460513 Please let me know if you're looking for a author for your blog. You have some really great posts and I believe I would be a good asset. If you ever want to take some of the load off, I'd really like to write some articles for your blog in exchange for a link back to mine. Please send me an e-mail if interested. Kudos! Please let me know if you’re looking for a author for your blog. You have some really great posts and I believe I would be a good asset. If you ever want to take some of the load off, I’d really like to write some articles for your blog in exchange for a link back to mine. Please send me an e-mail if interested. Kudos!

]]> By: andrew http://www.andrewlih.com/blog/2009/02/24/content-management-systems-reconsidered/comment-page-1/#comment-311669 andrew Tue, 03 Mar 2009 07:52:44 +0000 http://www.andrewlih.com/blog/?p=336#comment-311669 I agree that Drupal is a strange hybrid beast, that cannot be fully described as a CMS. But I would say that it has an "opinion" as described in the article. The nomenclature and taxonomy structure definitely enforces a viewpoint on how things should be organized that most implementers comply with. A true framework is generic like a Lego set, and I think Drupal is something slightly higher level than that. Not sure we even have a term for that. I agree that Drupal is a strange hybrid beast, that cannot be fully described as a CMS. But I would say that it has an “opinion” as described in the article. The nomenclature and taxonomy structure definitely enforces a viewpoint on how things should be organized that most implementers comply with. A true framework is generic like a Lego set, and I think Drupal is something slightly higher level than that. Not sure we even have a term for that.

]]> By: David Strauss http://www.andrewlih.com/blog/2009/02/24/content-management-systems-reconsidered/comment-page-1/#comment-311668 David Strauss Sun, 01 Mar 2009 22:48:56 +0000 http://www.andrewlih.com/blog/?p=336#comment-311668 Oh, and I responded on the linked blog about the "a CMS cannot be a framework" argument: http://sunlightlabs.com/blog/comments/posted/?c=364 Oh, and I responded on the linked blog about the “a CMS cannot be a framework” argument:

http://sunlightlabs.com/blog/comments/posted/?c=364

]]> By: David Strauss http://www.andrewlih.com/blog/2009/02/24/content-management-systems-reconsidered/comment-page-1/#comment-311667 David Strauss Sun, 01 Mar 2009 22:40:31 +0000 http://www.andrewlih.com/blog/?p=336#comment-311667 I think seeing Drupal as a CMS is inaccurate. Drupal is more like a framework that bundles CMS modules you can use, ignore, or often disable completely. The vast majority of Drupal's code is there to support a modular framework for supporting inversion of control (the menu system), templating (the theme layer), database abstraction, user management/authentication, input security (filter out XSS, etc.), permissions, logging, and the decorator pattern (hooks) for altering/extending current functionality. The CMS components (node, block, etc.) are lightweight modules running on top of that framework. When you ignore or disable them, Drupal becomes a PHP framework that can run head-to-head against other frameworks. I think seeing Drupal as a CMS is inaccurate. Drupal is more like a framework that bundles CMS modules you can use, ignore, or often disable completely. The vast majority of Drupal’s code is there to support a modular framework for supporting inversion of control (the menu system), templating (the theme layer), database abstraction, user management/authentication, input security (filter out XSS, etc.), permissions, logging, and the decorator pattern (hooks) for altering/extending current functionality.

The CMS components (node, block, etc.) are lightweight modules running on top of that framework. When you ignore or disable them, Drupal becomes a PHP framework that can run head-to-head against other frameworks.

]]>