<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
	<title>Articles&gt;Style Guides&gt;Rhetoric&gt;Usability</title>	<link>http://tc.eserver.org/dir/Articles/Style-Guides/Rhetoric/Usability</link>
	<description>A listing of the most recently indexed works about Articles and Style Guides and Rhetoric and Usability 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>Articles&gt;Style Guides&gt;Rhetoric&gt;Usability</title>
		<link>http://tc.eserver.org/dir/Articles/Style-Guides/Rhetoric/Usability</link>
	</image>
	<item>
		<title>Building a Better Style Guide</title>
		<link>http://tc.eserver.org/20926.html</link>
		<guid>http://tc.eserver.org/20926.html</guid>
		<description>Why are style guides so frequently created, but so rarely successful? All too often, businesses ask for a style guide as a&#xD;means to create a common look and feel, in the belief that it will solve usability problems and establish consistency&#xD;between applications – only to be disappointed in the results. Even if such a style guide is followed carefully, the&#xD;resulting interfaces may not meet usability goals.. This paper explores strategies for creating a style guide that is more&#xD;than a simplistic rules book. By making the style guide part of the process, it can be used to promote a shared vision, to&#xD;help the product meet business and usability requirements for consistency and…it may actually be used.</description>
	</item>
	<atom:link href="http://tc.eserver.org/dir/Articles/Style-Guides/Rhetoric/Usability.xml" rel="self" type="application/rss+xml"/>
</channel>
</rss>