Totally agree that users can have lots of difficulty when presented with Content Wysiwyg pages that allow the user to "get the feel" of what he is entering or creating is the real requirement. Complicated stuff should be kept to the end. We have seen many demo's of product that they say is easy, but it may be to the techies but not to the normal mortals.
Kind Regards Kay Kennedy NBS Solutions Email: [EMAIL PROTECTED] URL: www.nbs-solutions.com Tel: +44 (0)1293 442797 Fax: +44 (0)1293 565661 Privileged/confidential information and/or copyright material may be contained in this E-mail. This information and material is intended for the use of the addressee only, or the person responsible for delivering it to the intended addressee, and so you may not copy it or deliver it to anyone else, or use it in any unauthorised manner. To do so is prohibited and may be unlawful. If you receive this E-mail by mistake, please advise the sender immediately by using the reply facility in your E-mail software. -----Original Message----- From: Michael Kowalski [mailto:[EMAIL PROTECTED]] Sent: 30 January 2003 16:43 To: [EMAIL PROTECTED] Subject: Re: [cms-list] new to list/cm - What is CMS????? Well I'd more than just quibble with Emad's emphasis on "NOT pages". Of course a CMS must separate content from presentation (or "page structure" if you like). But from a usability perspective, it is very often better not to make that separation too explicit in the authoring process. I've often seen editorial users frankly baffled by complex hierarchies of content elements that do not (in their view) naturally map to their website structure. In many contexts, you can get the best of both worlds by offering WYSIWYG "page" authoring to editorial users and only separating out the content objects for reuse behind the scenes. Even where workflow or other concerns make authoring of smaller elements desirable, these still have to be edited through some interface: you can treat this document as a "page" also, albeit not a publishable one. We need to remember that CMS *users* are not interested in the theory of CMS: they have business problems to solve around authoring and managing content. We need to make that process as simple and intuitive as possible. michael -- http://cms-list.org/ more signal, less noise. -- http://cms-list.org/ more signal, less noise.
