<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
	<title>Articles&gt;Content Management&gt;Documentation&gt;Software</title>	<link>http://tc.eserver.org/dir/Articles/Content-Management/Documentation/Software</link>
	<description>A listing of the most recently indexed works about Articles and Content Management and Documentation and Software 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;Content Management&gt;Documentation&gt;Software</title>
		<link>http://tc.eserver.org/dir/Articles/Content-Management/Documentation/Software</link>
	</image>
	<item>
		<title>Hey Rocky – Watch Me Pull a CMS Out of My HAT</title>
		<link>http://tc.eserver.org/34351.html</link>
		<guid>http://tc.eserver.org/34351.html</guid>
		<description>When companies decide whether or not to adopt a CMS or continue using a HAT, there are many factors to consider. Perlin outlines elements of both CMSs and HATs that could help you determine which is best for your organization.</description>
	</item>
	<item>
		<title>Getting FLOSSy: Acrobat Killer Or HAT Replacement?</title>
		<link>http://tc.eserver.org/32146.html</link>
		<guid>http://tc.eserver.org/32146.html</guid>
		<description>Some writers truly hate Adobe Acrobat and any tool that can do the job better is worth a shot, particularly if it’s open source and easily navigated. Flossmanuals.net introduces FLOSS which does a lot of the single desktop Acrobat Pro’s job - collaboratively and open source.</description>
	</item>
	<atom:link href="http://tc.eserver.org/dir/Articles/Content-Management/Documentation/Software.xml" rel="self" type="application/rss+xml"/>
</channel>
</rss>