Avoid Problems

A CMS should support an open, standards-based architecture so that multiple data types work together. Ongoing development ideally should support dynamic HTML, XML, Java, .NET, and Web services, as well as other emerging technologies. A sound system should handle various content types to ensure compatibility with future technologies and protocols. (When a system supports only a specific content type, it is probable that at a later date, the retrofit of all existing content will be necessary.)

An open system goes beyond asset types and tools. There is also the issue of legacy content repositories (a fancy term for “old crap”). You never know when an old Web page, dusty data, or other archaic company information may be of value. With a flexible system in place, content discovery and reuse becomes possible at a global level, and the costs associated with the search for or duplication of content drops. Few content management solutions have this capability currently, although it can be a valuable tool.