Sent by Ron Derksen on 15 September 2003 13:01
Hi all,
Before I start, I apologize if this isn't really on-topic for this list.
At the company where I work, we use several technologies to build
websites: Lotus Domino/Notes, IBM WebSphere (Portal Server) and ASP.NET.
All of these products can produce nice looking websites, but standards
support is not an option. Especially Domino and WebSphere are very bad
at creating valid and semantically correct (X)HTML. ASP.NET uses several
objects that turn into invalid (X)HTML on the web.
Isn't it time for the WaSP organization to focus their attention on
these (and other) technologies, now that the browser wars are settled?
Most users are now reasonably able to view a site that's built with
standards, but if the server software churns out invalid HTML-code, it's
kind of useless.
Let's be honest, how many of you create static HTML sites? Most sites
nowadays (at least professionally created sites) use some kind of
backend system for content management, which involves a WYSIWYG editing
component. There aren't many tools out there (outside of the
blogging-tools) that create valid HTML-code.
I'm sure that WaSP will be able to convince and help the creators of
these tools to change their products, so that the web becomes the place
we all dream of ;-)
I'm interested in reading your opinions.
Ron Derksen
______________________________________________________________________
css-discuss [EMAIL-REMOVED]]
http://www.css-discuss.org/mailman/listinfo/css-d
Supported by evolt.org -- http://www.evolt.org/help_support_evolt/