<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>

<channel>
	<title>Writer River &#187; documentation</title>
	<atom:link href="http://writerriver.com/tag/documentation/feed/" rel="self" type="application/rss+xml" />
	<link>http://writerriver.com</link>
	<description>social news for technical communicators</description>
	<pubDate>Tue, 06 Jan 2009 18:13:17 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.3</generator>
	<language>en</language>
	<image>
  <link>http://writerriver.com</link>
  <url>http://writerriver.com/wp-content/favicon.gif</url>
  <title>Writer River</title>
</image>
		<item>
		<title>Coding Horror: How to Write Technical Documentation</title>
		<link>http://writerriver.com/2008/10/20/coding-horror-how-to-write-technical-documentation/</link>
		<comments>http://writerriver.com/2008/10/20/coding-horror-how-to-write-technical-documentation/#comments</comments>
		<pubDate>Mon, 20 Oct 2008 14:27:08 +0000</pubDate>
		<dc:creator>Tom Johnson</dc:creator>
		
		<category><![CDATA[Writer River]]></category>

		<category><![CDATA[documentation]]></category>

		<category><![CDATA[process]]></category>

		<guid isPermaLink="false">http://writerriver.com/2008/10/20/coding-horror-how-to-write-technical-documentation/</guid>
		<description><![CDATA[Coding Horror: How to Write Technical Documentation.]]></description>
			<content:encoded><![CDATA[<p><a href="http://www.codinghorror.com/blog/archives/000668.html">Coding Horror: How to Write Technical Documentation</a>.</p>]]></content:encoded>
			<wfw:commentRss>http://writerriver.com/2008/10/20/coding-horror-how-to-write-technical-documentation/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Collaborative Walkthrough Video:
 A uni &#8230;</title>
		<link>http://writerriver.com/2008/09/03/collaborative-walkthrough-video-a-uni/</link>
		<comments>http://writerriver.com/2008/09/03/collaborative-walkthrough-video-a-uni/#comments</comments>
		<pubDate>Wed, 03 Sep 2008 13:15:29 +0000</pubDate>
		<dc:creator>noel</dc:creator>
		
		<category><![CDATA[Writer River]]></category>

		<category><![CDATA[documentation]]></category>

		<category><![CDATA[User]]></category>

		<category><![CDATA[walkthrough]]></category>

		<guid isPermaLink="false">http://writerriver.com/2008/09/03/collaborative-walkthrough-video-a-uni/</guid>
		<description><![CDATA[Collaborative Walkthrough Video:
 A unique look at how other organizations deal with documentation design and critique. Plus some really good best practice tips.]]></description>
			<content:encoded><![CDATA[<p><a href="http://www.mirandabennett.com/onwriting/?p=23">Collaborative Walkthrough Video:</a></p>
<p> A unique look at how other organizations deal with documentation design and critique. Plus some really good best practice tips.</p>]]></content:encoded>
			<wfw:commentRss>http://writerriver.com/2008/09/03/collaborative-walkthrough-video-a-uni/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Best Practices for Editing Modular Docum &#8230;</title>
		<link>http://writerriver.com/2008/08/18/best-practices-for-editing-modular-docum/</link>
		<comments>http://writerriver.com/2008/08/18/best-practices-for-editing-modular-docum/#comments</comments>
		<pubDate>Mon, 18 Aug 2008 10:49:08 +0000</pubDate>
		<dc:creator>noel</dc:creator>
		
		<category><![CDATA[Writer River]]></category>

		<category><![CDATA[dita]]></category>

		<category><![CDATA[documentation]]></category>

		<guid isPermaLink="false">http://writerriver.com/2008/08/18/best-practices-for-editing-modular-docum/</guid>
		<description><![CDATA[Best Practices for Editing Modular Documentation]]></description>
			<content:encoded><![CDATA[<p><a HREF="http://www.writersua.com/articles/modular/index.html">Best Practices for Editing Modular Documentation</a></p>]]></content:encoded>
			<wfw:commentRss>http://writerriver.com/2008/08/18/best-practices-for-editing-modular-docum/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Proposed API for tools to help educate computer users online - O&#8217;Reilly News</title>
		<link>http://writerriver.com/2008/08/11/proposed-api-for-tools-to-help-educate-computer-users-online-oreilly-news/</link>
		<comments>http://writerriver.com/2008/08/11/proposed-api-for-tools-to-help-educate-computer-users-online-oreilly-news/#comments</comments>
		<pubDate>Tue, 12 Aug 2008 00:46:30 +0000</pubDate>
		<dc:creator>WorkingWriter</dc:creator>
		
		<category><![CDATA[Writer River]]></category>

		<category><![CDATA[community]]></category>

		<category><![CDATA[documentation]]></category>

		<category><![CDATA[education]]></category>

		<category><![CDATA[publishing]]></category>

		<category><![CDATA[training]]></category>

		<guid isPermaLink="false">http://writerriver.com/2008/08/11/proposed-api-for-tools-to-help-educate-computer-users-online-oreilly-news/</guid>
		<description><![CDATA[Here are some thoughts about how to help developers create adequate tools for educating users. The author asks for feedback on this draft. He shouldn&#8217;t just hear from developers and software architects.
Proposed API for tools to help educate computer users online - O&#8217;Reilly News.]]></description>
			<content:encoded><![CDATA[<p>Here are some thoughts about how to help developers create adequate tools for educating users. The author asks for feedback on this draft. He shouldn&#8217;t just hear from developers and software architects.</p>
<p><a href="http://news.oreilly.com/2008/08/proposed-api-for-tools-to-help.html">Proposed API for tools to help educate computer users online - O&#8217;Reilly News</a>.</p>]]></content:encoded>
			<wfw:commentRss>http://writerriver.com/2008/08/11/proposed-api-for-tools-to-help-educate-computer-users-online-oreilly-news/feed/</wfw:commentRss>
		</item>
		<item>
		<title>What You Leave in Your Wake</title>
		<link>http://writerriver.com/2008/08/07/what-you-leave-in-your-wake/</link>
		<comments>http://writerriver.com/2008/08/07/what-you-leave-in-your-wake/#comments</comments>
		<pubDate>Thu, 07 Aug 2008 08:33:15 +0000</pubDate>
		<dc:creator>shanghaitechwriter</dc:creator>
		
		<category><![CDATA[Writer River]]></category>

		<category><![CDATA[documentation]]></category>

		<guid isPermaLink="false">http://writerriver.com/2008/08/07/what-you-leave-in-your-wake/</guid>
		<description><![CDATA[What You Leave in Your Wake]]></description>
			<content:encoded><![CDATA[<p><a href="http://www.dmncommunications.com/weblog/?p=363">What You Leave in Your Wake</a></p>]]></content:encoded>
			<wfw:commentRss>http://writerriver.com/2008/08/07/what-you-leave-in-your-wake/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Beijing Olympics Style Guide</title>
		<link>http://writerriver.com/2008/08/06/beijing-olympics-style-guide/</link>
		<comments>http://writerriver.com/2008/08/06/beijing-olympics-style-guide/#comments</comments>
		<pubDate>Thu, 07 Aug 2008 02:15:12 +0000</pubDate>
		<dc:creator>shanghaitechwriter</dc:creator>
		
		<category><![CDATA[Writer River]]></category>

		<category><![CDATA[Beijing]]></category>

		<category><![CDATA[documentation]]></category>

		<category><![CDATA[Olympics]]></category>

		<category><![CDATA[style guide]]></category>

		<category><![CDATA[technical writing]]></category>

		<guid isPermaLink="false">http://writerriver.com/2008/08/06/beijing-olympics-style-guide/</guid>
		<description><![CDATA[Beijing Olympics Style Guide]]></description>
			<content:encoded><![CDATA[<p><a href="http://www.shanghaitechwriter.com/2008/08/07/beijing-olympics-style-guide/">Beijing Olympics Style Guide</a></p>]]></content:encoded>
			<wfw:commentRss>http://writerriver.com/2008/08/06/beijing-olympics-style-guide/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Is printed documentation dead?</title>
		<link>http://writerriver.com/2008/08/05/is-printed-documentation-dead/</link>
		<comments>http://writerriver.com/2008/08/05/is-printed-documentation-dead/#comments</comments>
		<pubDate>Tue, 05 Aug 2008 07:04:25 +0000</pubDate>
		<dc:creator>shanghaitechwriter</dc:creator>
		
		<category><![CDATA[Writer River]]></category>

		<category><![CDATA[documentation]]></category>

		<category><![CDATA[print]]></category>

		<category><![CDATA[trend]]></category>

		<guid isPermaLink="false">http://writerriver.com/2008/08/05/is-printed-documentation-dead/</guid>
		<description><![CDATA[Is printed documentation dead?]]></description>
			<content:encoded><![CDATA[<p><a href="http://www.dmncommunications.com/weblog/?p=373">Is printed documentation dead?</a></p>]]></content:encoded>
			<wfw:commentRss>http://writerriver.com/2008/08/05/is-printed-documentation-dead/feed/</wfw:commentRss>
		</item>
		<item>
		<title>22 things to check before publishing a t &#8230;</title>
		<link>http://writerriver.com/2008/08/05/22-things-to-check-before-publishing-a-t/</link>
		<comments>http://writerriver.com/2008/08/05/22-things-to-check-before-publishing-a-t/#comments</comments>
		<pubDate>Tue, 05 Aug 2008 07:00:35 +0000</pubDate>
		<dc:creator>shanghaitechwriter</dc:creator>
		
		<category><![CDATA[Writer River]]></category>

		<category><![CDATA[checklist]]></category>

		<category><![CDATA[documentation]]></category>

		<category><![CDATA[publishing]]></category>

		<category><![CDATA[review]]></category>

		<guid isPermaLink="false">http://writerriver.com/2008/08/05/22-things-to-check-before-publishing-a-t/</guid>
		<description><![CDATA[22 things to check before publishing a technical manual]]></description>
			<content:encoded><![CDATA[<p><a href="http://www.helpscribe.com/2008/07/22-things-to-check-before-publishing.html">22 things to check before publishing a technical manual</a></p>]]></content:encoded>
			<wfw:commentRss>http://writerriver.com/2008/08/05/22-things-to-check-before-publishing-a-t/feed/</wfw:commentRss>
		</item>
		<item>
		<title>How I write Help for a topic-based help  &#8230;</title>
		<link>http://writerriver.com/2008/08/05/how-i-write-help-for-a-topic-based-help/</link>
		<comments>http://writerriver.com/2008/08/05/how-i-write-help-for-a-topic-based-help/#comments</comments>
		<pubDate>Tue, 05 Aug 2008 06:59:42 +0000</pubDate>
		<dc:creator>shanghaitechwriter</dc:creator>
		
		<category><![CDATA[Writer River]]></category>

		<category><![CDATA[documentation]]></category>

		<category><![CDATA[help]]></category>

		<guid isPermaLink="false">http://writerriver.com/2008/08/05/how-i-write-help-for-a-topic-based-help/</guid>
		<description><![CDATA[How I write Help for a topic-based help system]]></description>
			<content:encoded><![CDATA[<p><a href="http://heidilhansen.blogspot.com/2008/07/how-i-write-help-for-topic-based-help.html">How I write Help for a topic-based help system</a></p>]]></content:encoded>
			<wfw:commentRss>http://writerriver.com/2008/08/05/how-i-write-help-for-a-topic-based-help/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Community and documentation - what&#8217;s the best blend?</title>
		<link>http://writerriver.com/2008/08/04/community-and-documentation-whats-the-best-blend/</link>
		<comments>http://writerriver.com/2008/08/04/community-and-documentation-whats-the-best-blend/#comments</comments>
		<pubDate>Mon, 04 Aug 2008 14:33:08 +0000</pubDate>
		<dc:creator>annegentle</dc:creator>
		
		<category><![CDATA[Writer River]]></category>

		<category><![CDATA[community]]></category>

		<category><![CDATA[documentation]]></category>

		<category><![CDATA[FAQs]]></category>

		<category><![CDATA[forums]]></category>

		<category><![CDATA[wikis]]></category>

		<guid isPermaLink="false">http://writerriver.com/?p=91</guid>
		<description><![CDATA[O&#8217;Reilly editor Andy Oram has an excellent article about community-based documentation where he shares his research findings - and it&#8217;s not all sugar-coated. Only about half of forum questions are answered correctly, and when a user needs more training or indepth explanations on complex products or configurations, the community can sometimes let them down. Community [...]]]></description>
			<content:encoded><![CDATA[<p>O&#8217;Reilly editor Andy Oram has an excellent article about community-based documentation where he shares his research findings - and it&#8217;s not all sugar-coated. Only about half of forum questions are answered correctly, and when a user needs more training or indepth explanations on complex products or configurations, the community can sometimes let them down. Community leaders learn quickly that they can become targets when trying to explain that a task is difficult or complicated. See <a href="http://praxagora.com/andyo/professional/community_author_collaboration.html">Educating computer users: the need for community/author collaboration.</a> Find out when documentation deserves further polishing. Excellent insights.</p>]]></content:encoded>
			<wfw:commentRss>http://writerriver.com/2008/08/04/community-and-documentation-whats-the-best-blend/feed/</wfw:commentRss>
		</item>
	</channel>
</rss>
