Hey Guys I thought I'd kick off a little bit of discussion on this board - topic of the day:
What are the options in terms of building standards support into CMS type products? Many CMS products tout themselves as being XHTML compliant - yadda, yadda. But how does this play out in the real world. From where I stand I can see a bunch of options in implementing this type of support: 1) In the editor, only let users create content in the editor that is compliant. What sort of support is there for this kind of thing among the currently available editors? How do you give the user sufficient control over presentation while maintaining control of the code & not constantly stuffing XHTML compliance down the user's throat? 2) Between the editor and the data store. This one is kind of a cop out, but its pretty easily implemented. The sad facts as I see them are that the current range of editors have a pretty woeful record when it comes to generating stand compliant code - however tidy & jtidy are super easy to get hold of and pipe rough HTML content through in order to get clean XHTML at the other end. The downside of this is that users might see one thing in the editor and other when the content reaches the web. 3) Entire site parsing, give the administrator the ability to run a tool over the whole site & parse it into a valid XHTML format. 4) Parse content on output, escaping/encoding special characters, etc... Personally I think output is a very inefficient place to be doing this sort of stuff, but I know it can and is done here. 5) Other? Anyway I'm interested in people thoughts here because I have yet to see a really nice & neat solution. Cheers Mark ------------------ Mark Stanton Technical Director Gruden Pty Ltd Tel: 9956 6388 Mob: 0410 458 201 Fax: 9956 8433 http://www.gruden.com ********************************************************* The CMS discussion list for http://webstandardsgroup.org/ *********************************************************
