<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
	<title>Wylie, Ann</title>	<link>http://tc.eserver.org/authors/Wylie,_Ann</link>
	<description>A bibliography of works by Wylie, Ann 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>Wylie, Ann</title>
		<link>http://tc.eserver.org/dir/Wylie,_Ann</link>
	</image>
	<item>
		<title>Don&apos;t Forget A Strategy for Microcontent—Headlines, Decks, Buttons and Links—When You Redesign Your Site</title>
		<link>http://tc.eserver.org/31510.html</link>
		<guid>http://tc.eserver.org/31510.html</guid>
		<description>Little things mean a lot. Especially online. Microcontent—or the headlines, decks, subheads and other &apos;small&apos; pieces of web copy—actually do most of the communicating on your web site. Handled poorly, microcontent can confuse and frustrate web visitors. Here&apos;s how to write microcontent to communicate to—instead of discombobulate—your readers.</description>
	</item>
	<item>
		<title>Use Presentation Copy--Headlines, Decks and More--To Reach Flippers and Skimmers</title>
		<link>http://tc.eserver.org/31401.html</link>
		<guid>http://tc.eserver.org/31401.html</guid>
		<description>I&apos;m often amazed at how much energy writers put into perfecting the analogy in the 32nd paragraph of their piece when those same folks toss off a headline in the 17 seconds before happy hour on a Friday night.&#xD;&#xD;The sad truth is, most of your readers will never see the 32nd paragraph of your brilliant copy. But many more of them will read the headline.</description>
	</item>
	<atom:link href="http://tc.eserver.org/authors/Wylie,_Ann.xml" rel="self" type="application/rss+xml"/>
</channel>
</rss>