<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
	<title>Stuhlemmer, Barbara</title>	<link>http://tc.eserver.org/authors/Stuhlemmer,_Barbara</link>
	<description>A bibliography of works by Stuhlemmer, Barbara 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>Stuhlemmer, Barbara</title>
		<link>http://tc.eserver.org/dir/Stuhlemmer,_Barbara</link>
	</image>
	<item>
		<title>Saving Money With Virtual Teams and Working at a Distance Without Travel</title>
		<link>http://tc.eserver.org/33700.html</link>
		<guid>http://tc.eserver.org/33700.html</guid>
		<description>In this article, I will identify some of the tools we have used to bring together contractors, writers, and clients for our projects. Often, to determine a tool’s value, I will use a trial version. Some tools are very valuable but cost more, while others are functional and free. Although I cannot recommend which tools are best for your organization, I do recommend trying those tools that might fit your needs.</description>
	</item>
	<item>
		<title>Authoring in XML -- Why Start?</title>
		<link>http://tc.eserver.org/32180.html</link>
		<guid>http://tc.eserver.org/32180.html</guid>
		<description>As techcom professionals, we have been talking about authoring in XML for a very long time. At first, it was a lot of hype about a format that required major programming skills and had zero tools’ support, but that is now changing. Today, there are hundreds, if not thousands, of tools that support XML and a standard called DITA that is in constant development to support content publishing for different industries. As a result, more and more companies seem to be embracing this content format.If you are a writer or techcom manager who is encouraging your company to make this change, then what do you need to know to prepare?</description>
	</item>
	<item>
		<title>Content Management: When Do We Need It?</title>
		<link>http://tc.eserver.org/31169.html</link>
		<guid>http://tc.eserver.org/31169.html</guid>
		<description>By ensuring a document process is put in place and all people in your company know where to find information, how to request changes, update, and distribute new content, and who has the permission to manage the content you will be well on your way to having a viable content management system. Adding the software to automatically manage the content will only come when core principles of the organization require it.</description>
	</item>
	<item>
		<title>Converting to XML: Some Point-Form Pros and Cons</title>
		<link>http://tc.eserver.org/31168.html</link>
		<guid>http://tc.eserver.org/31168.html</guid>
		<description>I have recently converted some user documents from MS Word to XML for a medical device company with the intent that they would be looking at authoring their future end-user documentation (printed, embedded, and online) in XML. I want to share with you some of the triumphs and challenges we had met along the way.</description>
	</item>
	<item>
		<title>What They&apos;re Saying About CMS and XML</title>
		<link>http://tc.eserver.org/31170.html</link>
		<guid>http://tc.eserver.org/31170.html</guid>
		<description>Assuming the tools are now within the range of an average small to medium business and all the other costs associated with implementation are still there, what incentive is there for a business to want to change to CMS or XML?</description>
	</item>
	<atom:link href="http://tc.eserver.org/authors/Stuhlemmer,_Barbara.xml" rel="self" type="application/rss+xml"/>
</channel>
</rss>