<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
	<title>Articles&gt;Writing&gt;Technical Writing&gt;Community</title>	<link>http://tc.eserver.org/dir/Articles/Writing/Technical-Writing/Community</link>
	<description>A listing of the most recently indexed works about Articles and Writing and Technical Writing and Community 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;Writing&gt;Technical Writing&gt;Community</title>
		<link>http://tc.eserver.org/dir/Articles/Writing/Technical-Writing/Community</link>
	</image>
	<item>
		<title>Sometimes It&apos;s Nice to be Reminded There’s a Whole Community of Technical Writers Out There</title>
		<link>http://tc.eserver.org/32085.html</link>
		<guid>http://tc.eserver.org/32085.html</guid>
		<description>The Content Wrangler’s 10 DITA lessons learned from Tech Writers in the Trenches really nails down some vital things you should know if you want to implement DITA. More than that though, you can apply the lessons learned here to almost any project, not just technical writing and not just implementing new software.</description>
	</item>
	<item>
		<title>Pith and Vinegar: Is Technical Writing Your Calling?</title>
		<link>http://tc.eserver.org/28958.html</link>
		<guid>http://tc.eserver.org/28958.html</guid>
		<description>An essay exploring whether technical writing is a &apos;calling.&apos;</description>
	</item>
	<atom:link href="http://tc.eserver.org/dir/Articles/Writing/Technical-Writing/Community.xml" rel="self" type="application/rss+xml"/>
</channel>
</rss>