Why Getting Laid Off is Better than Building a Proprietary CMS
You have to appreciate CMSwatch's editor's ability to write a headline that grabs and holds the reader. They published an article by Barry Bealer in August, entitled Why Getting Laid Off is Better than Building a Proprietary CMS. We agree that corporate IT departments starting to build a "from-the-ground-up" Content Management Systems in 2002 ought to have their collective heads examined. Everyone should begin a content management project by building on a CMS platform that has been used in other projects of similar scope and importance.
However, notice that the opinion piece does not call upon all corporations to license one of the expensive, enterprise-level content management systems like Vignette or Broadvision. According to the article: "The more open the solution, the better able you are to complete system maintenance and upgrades and the less tied to a resource you are. The key is to be sure your system is built using industry standards and is well documented."
There are lots of publishing systems, including big, expensive solutions, less expensive commercial solutions like Manila, and Open Source solutions like Zope and Midgard. BTW, how can the folks at CMSwatch leave out systems like Slashcode and Bricolage?
Hat tip for locating this goes to Camworld.