217
 | | Require CSS & XHTML compliance
While huge improvements have been made, it is still tough to create DNN sites that only use CSS and XHTML.
The core should no longer use tables and a sample CSS only/XHTML compliant skin should be included with the default installation.
Eventually any optional and 3rd party modules shoud be required to also comply before being eligible to get listed in the marketplace.
Problem:
CSS skins are elegant and provide great usability, but are still not supported by DNN's default install. DNN does not pass XHTML validation out of the box.
Rationale:
CSS and XHTML compliance is increasingly required for adoption by many organizations.
Inclusion in the core product would relieve many designers form having to duplicate their efforts trying to modify the core.
Solution:
Add a requirement to the DNN release cycle that the product, with the optional skin installed, pass the W3C Validator at http://validator.w3.org/
Impact:
The forums have a fair amount of analysis and description of what would be required. In particular see the entry at http://www.dotnetnuke.com/Community/Forums/tabid/795/forumid/-1/threadid/138395/scope/posts/Default.aspx
Risk:
Unknown. some existing skins may have dependencies on the current settings. If so, then there may need to be a portal by portal setting made to determine what HTML gets output for that portal.
Created: 6/30/2007 11:24:34 AM by John Cornelison
Scheduled For Version:
Delivered In Version: | |