Jeff WhatCott,
Acquia, asked some important and thought provoking questions on his blog, "
A Dormant Drupal Opportunity". While the post focuses on Drupal, I think the contents of his post can apply to almost any content management system (CMS) out there.
In the article, Jeff asks whether defining Drupal as a CMS does more harm than good in describing the scope of features Drupal has to offer. In his words, the term CMS is a "20th century term that completely undersells what Drupal is capable of" as social software and a means for collaboration. Considering I really didn't understand what a CMS was until the 21st century, I beg to differ that the term CMS is as ancient as he makes it sound. However, he is entirely correct...many of today's Web applications that we call a CMS, really are
not just a CMS.
Jeff asks three questions in his post: