
Usually, the one thing missing from the planning of a WCM-driven web site is what's most likely to shoot the implementation in the foot: the functional design of the CMS back-end. The form and function of how the CMS will work, look and feel for the end-user of the system, not the visitor to the web site, is too often overlooked. This is odd: isn't the rationale for getting a CMS in the first place usually based on some kind of ROI in efficiency in actually producing the content and sites? View both works by Bloem, Adriaan View all 15 works published by CMSwatch |