<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
	<title>Articles&gt;TC&gt;Writing&gt;Minimalism</title>	<link>http://tc.eserver.org/dir/Articles/TC/Writing/Minimalism</link>
	<description>A listing of the most recently indexed works about Articles and TC and Writing and Minimalism in the field of technical communication (and technical writing).</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;TC&gt;Writing&gt;Minimalism</title>
		<link>http://tc.eserver.org/dir/Articles/TC/Writing/Minimalism</link>
	</image>
	<item>
		<title>Professionalizing Plain Language: A Postcard on Current Developments</title>
		<link>http://tc.eserver.org/34130.html</link>
		<guid>http://tc.eserver.org/34130.html</guid>
		<description>With the passing of the Brayley Bill in Congress, the significance of plain language has become even more apparent to technical communicators. The author lays out a step-by-step plan to maintain the relevance of plain language as an important and necessary profession.</description>
	</item>
	<item>
		<title>Applying Minimalist Principles, Strategies, and Techniques</title>
		<link>http://tc.eserver.org/19839.html</link>
		<guid>http://tc.eserver.org/19839.html</guid>
		<description>People use documentation differently from what we might expect. They don’t like to read; instead they jump to a&#xD;task with prior knowledge, and sometimes don’t realize&#xD;they’ve made an error. Understanding how users learn&#xD;and applying John Carroll’s minimalist principles will&#xD;help provide solutions to this problem.&#xD;Documentation that has been successfully planned and&#xD;designed for minimalism may take longer to create than&#xD;other manuals, but reaps the benefits of making users&#xD;more productive and happy, while reducing support calls,&#xD;maintenance, translation, and publishing costs. The key&#xD;factors to a successful minimalist approach (or any good&#xD;documentation design) are a keen understanding of your&#xD;users, prototypes designed to match tasks relevant to&#xD;users, and iterative testing to improve each draft.</description>
	</item>
	<atom:link href="http://tc.eserver.org/dir/Articles/TC/Writing/Minimalism.xml" rel="self" type="application/rss+xml"/>
</channel>
</rss>