> I fully agree that a CMS should store a <headline> rather than a <div> > with style, but why do you assume a _good_ WYSIWYG can't present the > author with a styled view (not just preview) in authoring time, while > saving off structured content?
There *are* some problems with it, though. Namely if it shows styles directly, then an author may be compelled to allow the visual presentation of an element to represent their own stuctural meaning. "hey...I really like the color of the headline, I think I'm going to use that for my blockquote as it really sets it off as a quotation." -- IK -- Yes, but a) form based content entry does not prevent content being entered in the 'wrong' field in addition to being not very flexible to begin with, b) a good WYSIWYG editor could validate to a client-defined schema to prevent this problem. and from Darrel's next message: I think I may have asked this previously, but are any CMSs using a WYSIWYG-like editor that draws the style widgets directly from a CSS or XLST document? I'd like to see a simple editor that has the ability to pull in a set of XML tags and CSS based on the type of document being created and then only showing and rendering the tags available for that particular piece of content. For instance, if the author is creating a press release, It would only bring in and style the following XML tags: title, date, location, author, quote. -- IK -- Yes there are such WYSIWYG editors, ours (liveSTORYBOARD CMS) being one of them, and I am sure there are others. Xopus is similar. In our case, we transform a RELAX NG schema to JS objects to aid in our validation and to present in the UI only valid formatting choices. We do what you mentioned above, but also, as the user clicks around elements even in a more general template like a generic article, they are presented only with valid replacements or children of the current tag they are in. We believe this approach is the best of both worlds. best, Iva -- http://cms-list.org/ trim your replies for good karma.
