<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
	<title>Design&gt;Web Design&gt;Style Guides</title>	<link>http://tc.eserver.org/dir/Design/Web-Design/Style-Guides</link>
	<description>A listing of the most recently indexed works about Design and Web Design and Style Guides in the field of technical communication.</description>
	<language>en-us</language>
	<copyright>Copyright (c) 2005-08 by the EServer. All rights reserved.</copyright>
	<managingEditor>tclib-editorial@eserver.org (TC Library Editorial Board)</managingEditor>
	<webMaster>webmaster@eserver.org (Geoffrey Sauer)</webMaster>
	<image>
		<url>http://tc.eserver.org/images/newlogo.gif</url>
		<title>Design&gt;Web Design&gt;Style Guides</title>
		<link>http://tc.eserver.org/dir/Design/Web-Design/Style-Guides</link>
	</image>
	<item>
		<title>A Web Policy is a Policy, Not a Standard</title>
		<link>http://tc.eserver.org/34451.html</link>
		<guid>http://tc.eserver.org/34451.html</guid>
		<description>I&apos;ve noticed recently that people (and organizations) often interchange the policies and standards labels as if there is no difference between them... like those who insist the Web and the Internet are the same. I&apos;m not one for splitting hairs, but in this case, policies are truly not the same as standards and it&apos;s important to be clear about the distinction.</description>
	</item>
	<item>
		<title>Web Design Standards: 10 Organizational Secrets</title>
		<link>http://tc.eserver.org/27389.html</link>
		<guid>http://tc.eserver.org/27389.html</guid>
		<description>The practices and processes that facilitate the organizational development needed to create a successful Web design standard.</description>
	</item>
	<item>
		<title>Style Guides</title>
		<link>http://tc.eserver.org/26836.html</link>
		<guid>http://tc.eserver.org/26836.html</guid>
		<description>Style guides are used to provide a consistent look and feel. They should be defined as part of usability requirements and conformance should be monitored during development.</description>
	</item>
	<item>
		<title>Corporate Pages 2002-2004 (Part 2)</title>
		<link>http://tc.eserver.org/26138.html</link>
		<guid>http://tc.eserver.org/26138.html</guid>
		<description>When training web authors, I prefer to use good examples of their kind, so these must have been either typical or among the best I could find at the time. However, they certainly did not contain content to skite about.</description>
	</item>
	<item>
		<title>Standards for Online Content Authors</title>
		<link>http://tc.eserver.org/26128.html</link>
		<guid>http://tc.eserver.org/26128.html</guid>
		<description>The standards on this page include non-technical standards relevant to all web authors and technical standards relevant to some web authors.</description>
	</item>
	<item>
		<title>Guideline Dogma</title>
		<link>http://tc.eserver.org/26087.html</link>
		<guid>http://tc.eserver.org/26087.html</guid>
		<description>Nobody would deny that usability guidelines, applied in context by a usability professional, are extremely valuable in guiding a website evaluation. The problem occurs when non-professionals apply these guidelines out of context. This can result in an unimaginative site that looks bland and homogenous. To design usable sites that truly engage customers we need to replace simple guidelines with a customer-centred design process.</description>
	</item>
	<item>
		<title>Colour Design and Tools</title>
		<link>http://tc.eserver.org/25754.html</link>
		<guid>http://tc.eserver.org/25754.html</guid>
		<description>With cartography on the Web, the use of colour plays an important role in the visualization and analysis of data. The correct application of colour for the display of thematic map data, allows for the better observation of interrelationships and patterns.</description>
	</item>
	<item>
		<title>Using a WWW Development Design Document to Create a Comprehensive Web Site</title>
		<link>http://tc.eserver.org/24275.html</link>
		<guid>http://tc.eserver.org/24275.html</guid>
		<description>Technical Communicators are eminently qualified for Web publishing as it is a natural extension of our writing abilities. However, we must be careful to avoid the pitfalls of Web publishing and contribute to the host of glamorous Web sites that lack content, are difficult to navigate, and do not satisfy the ultimate goals of the organization or institution the site represents. One proven technique for planning and implementing a Web site is the creation of a WWW Development Design Document. By championing the development of this document, communicators return to their knowledge roots of organization and writing.</description>
	</item>
	<item>
		<title>Making Guidelines Part of the Team</title>
		<link>http://tc.eserver.org/22481.html</link>
		<guid>http://tc.eserver.org/22481.html</guid>
		<description>Guidelines. We seem to have a love-hate relationship with them. At the same time we construct them, we worry they’ll come back to haunt us. How did guidelines get such a bad reputation?</description>
	</item>
	<item>
		<title>Stylesheet or Stylesite? A Case Study</title>
		<link>http://tc.eserver.org/20340.html</link>
		<guid>http://tc.eserver.org/20340.html</guid>
		<description>CNET’s Stylesite for the Technology Department’s Documentation and Training group provides an online resource for writers and trainers. The continuing development of this tool encompasses site development,&#xD;content creation, and a fluid process of drafting standards. The site observes many of the same rules &apos;imposed&apos; upon the writers, and offers them a rare opportunity to collaborate with their editor in the&#xD;production of a manual of style.</description>
	</item>
	<item>
		<title>Style Guide for Online Hypertext</title>
		<link>http://tc.eserver.org/10042.html</link>
		<guid>http://tc.eserver.org/10042.html</guid>
		<description>When writing for the Web, the documents usually become part of a larger collection. It&apos;s important that the site follows a common structure so all documents are available in a logical place. For a document, the style is also very important. By using a common style, you ensure that a reader can use the site effectively. Some important aspects are indicating the status of the document, using images and icons, and writing in a device-independent way.</description>
	</item>
	<atom:link href="http://tc.eserver.org/dir/Design/Web-Design/Style-Guides.xml" rel="self" type="application/rss+xml"/>
</channel>
</rss>