From: Johan Steenkamp
I think we are talking about a java-based CMS, so I guess JSP (as opposed to PHP, ASP etc.) that generates valid output. Right?
In the end the CMS server technology is not really an issue. It is how the developers have used the technology to create the CMS output. For example if they generate a dynamic page and use invalid X/HTML markup then the page will of course not validate.
Sorry about not being clear: Yes indeed, I mean a Java based, server side cms/blog. Examples: roller, pebble, blojsom.
Basically the problem is that these systems can be so automatic that the user cannot completely control the emitted xhtml/css. Typically this means either a table-centric design or bad xhtml/css.
Since yesterdays mailing, I've discussed this with one of the authors (pebble) and he's been considering conversion toward xhtml/css.
I have to admit being quite surprised at this lack of control over the xhtml/css output because Java has some really great solutions in that space, and the religion of MVC (Model, View, Controller) is very well intrenched. Velocity is a terrific templating engine.
Interesting Cathedral vs Bazaar problem, I suspect.
Let me know if you know of a good Java solution!
Owen
********************************************************* The CMS discussion list for http://webstandardsgroup.org/ *********************************************************
