Generic Web Style Guide - free for the taking
A recent silverorange project had us cleaning up years of archived HTML pages to be more accessible and XHTML compliant. Cleaning up what was already there was time consuming, but easy enough. The more important task is making sure things stay accessible and valid. As the client will be continuing to manage the site and create new content, we’ve prepared a style guide to help those producing new pages and editing the current pages.
The guide covers the basics of web content creation, including basic XHTML/CSS guidelines, validation, writing guidelines, and consistency.
As the concepts are likely to be common to a lot of websites, we’re making the style guide available under the Creative Commons Attribution-ShareAlike License. Feel free to use this with your clients. We would also welcome any comments or improvements.
Thanks to the New York Public Library’s online style guide for reference and inspiration.
Keep up the great work. Hope the sun's shining in your beautiful city.
http://labs.silverorange.com/archives/2003/august/styleguide
which gives a 404, as the page seems to be at:
http://labs.silverorange.com/archives/2003/august/genericwebstyle
Also, the page does not validate, as the info div is labelled with an id, but it appears more than once in the document, which an id can't do. (Try to validate it with the W3C HTML Validator.)
Other than that, it's a great resource! ;)
1) In §1.2, subtopic "Use quotes for all attributes", second paragraph (after the example), reads: "The 'nowrap' attributed for ..." s/b "The 'nowrap' attribute"
2) also in §1.2, subtopic "Do not use depreciated tags" s/b "Do not use deprecated tags". This correction should also be made in the first sentence of the paragraph that follows, viz.: "Some tags that ... have been depreciated ...." s/b "Some tags that ... have been deprecated ...."
3) In §2.2, "Special Text-Formatting Classes", first paragraph, second sentence reads: "However, in certain instanced ...." s/b "However, in certain instances ...."
4) In §3.1, "Site visitors are your most important priority, first paragraph, first sentence reads: "This may seem obvious ... but it's vital important ...." s/b "This may seem obvious ... but it's vitally important ...."
5) In §3.2, "Do not specify fonts", third sentence reads: "If you want to add meaning to you text ...." s/b "If you want to add meaning to your text ...."
I have other suggestions, but these were the most egregious errors.
Other than that, the document has proven quite useful: I'm also developing a set of guidelines, and this was an excellent starting-point.
Kurtis
"If you want to add meaning to you text ..."
The last bit should read: "to your text".
It's great to see such good content


