[WSG] LOC new release

2005-04-19 Thread Douglas Clifton
The US Library of Congress (LOC) has today released the first of
a series of upgrades to their Web site. As you will see if you visit:

http://www.loc.gov/

The new design uses tableless layout, full use of CSS, XHTML
and improved usability, accessibility and aesthetics. I sent them
an email today, as they are still not encoding ampersands in
their URIs, but other than that the code should also validate.
The CSS could definitely use some cleaning up and reduction,
but this is progress -- from an organization with clout.

Nice site, check it out.

On another note, I am building a resource directory for Web
developers, designers and programmers. If anyone would
like to contribute resource suggestions, please contact me
off the list. The URI to the Web Standards category is:

http://loadaveragezero.com/app/drx/Internet/WWW/Design_and_Development/Standards

Thanks,

Doug-- Douglas Clifton[EMAIL PROTECTED]http://loadaveragezero.com/




RE: [WSG] LOC new release - standards or looks?

2005-04-19 Thread Paul Bennett



Thanks 
for the heads up Doug,

This 
is great news and good to see that developers are really picking up on standards 
compliant design and working that into projects of this 
scale.
The 
site does not yetvalidate and the encoded ampersands are a big issue in 
this (in fact the only issue on the front page)

One 
issue I have noticed is that some major developer sites and 'famous' css layout 
based sites actually don't validate. Is there a trend growing 
that people are building css based sites for the 'look' and not 
actuallycaring aboutstandards? Is it becoming about a 
'style'?

For 
example, a large site I work onwas redesigned recently (before I arrived) and the company specified that 
the code must validate. From wading through the muck they produced it appears 
that all the development company did was add a doctype to each page and 
for them this was 'valid code'. Worse, the site was built in nested tables (you 
go through 3 nested tables before hitting the actual page content) and the 
doctype in no way reflects the code or structure of the site. We are a LONG way 
from validating and it will be me that cleans up the 
mess.

Has 
anyoneelse noticed this kind oflip-service being paidto 
standards by devlopers?