<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
	<title>Design&gt;Publishing&gt;Web Design&gt;Usability</title>	<link>http://tc.eserver.org/dir/Design/Publishing/Web-Design/Usability</link>
	<description>A listing of the most recently indexed works about Design and Publishing and Web Design 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>Design&gt;Publishing&gt;Web Design&gt;Usability</title>
		<link>http://tc.eserver.org/dir/Design/Publishing/Web-Design/Usability</link>
	</image>
	<item>
		<title>Creating a Usable Electronic Newsletter In House</title>
		<link>http://tc.eserver.org/19196.html</link>
		<guid>http://tc.eserver.org/19196.html</guid>
		<description>Many organizations are opting to convert existing print publications into electronic newsletters (e-newsletters)—and for good reason. E-newsletters can be developed for a fraction of the cost of their print counterparts and delivered to a global audience instantly. While marketers are discovering the ease of reaching a target audience with e-mail, many e-mail users are frustrated by the barrage of e-newsletters that muddle their inboxes monthly, weekly, or even daily. An onslaught of unsolicited commercial e-mail (spam) has made readers wary of marketing attempts. To reach these wary readers, companies need to create e-newsletters that respond to their audience’s specific needs—namely usability and trust. By following a few guidelines, you can launch a usable and successful e-newsletter.</description>
	</item>
	<atom:link href="http://tc.eserver.org/dir/Design/Publishing/Web-Design/Usability.xml" rel="self" type="application/rss+xml"/>
</channel>
</rss>