<?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"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Wadeware &#187; Technical Documentation</title>
	<atom:link href="http://www.wadeware.net/category/technical-documentation/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.wadeware.net</link>
	<description>IT Consulting + Training &#38; Support</description>
	<lastBuildDate>Tue, 17 Jan 2012 21:30:33 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
		<item>
		<title>URLs: To see, or not to see? That is the question…</title>
		<link>http://www.wadeware.net/technical-documentation/urls-to-see-or-not-to-see-that-is-the-question/</link>
		<comments>http://www.wadeware.net/technical-documentation/urls-to-see-or-not-to-see-that-is-the-question/#comments</comments>
		<pubDate>Mon, 13 Jun 2011 22:26:57 +0000</pubDate>
		<dc:creator>Steve Wacker</dc:creator>
				<category><![CDATA[Technical Documentation]]></category>
		<category><![CDATA[Best Practices]]></category>
		<category><![CDATA[discussions]]></category>
		<category><![CDATA[editing]]></category>
		<category><![CDATA[hypertext]]></category>
		<category><![CDATA[Rants and Raves]]></category>
		<category><![CDATA[Tips]]></category>
		<category><![CDATA[URLs]]></category>
		<category><![CDATA[writing]]></category>

		<guid isPermaLink="false">http://www.wadeware.net/?p=1949</guid>
		<description><![CDATA[This post provides a bit of history about hypertext and discusses different options for displaying hyperlinks. It also seeks input from readers about whether full URLs (hyperlinks) are useful and their preferences for how URLs display.]]></description>
		<wfw:commentRss>http://www.wadeware.net/technical-documentation/urls-to-see-or-not-to-see-that-is-the-question/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>How to Discover Your Business Requirements</title>
		<link>http://www.wadeware.net/technical-documentation/how-to-discover-your-business-requirements/</link>
		<comments>http://www.wadeware.net/technical-documentation/how-to-discover-your-business-requirements/#comments</comments>
		<pubDate>Mon, 18 Apr 2011 20:47:47 +0000</pubDate>
		<dc:creator>Holly Amundson</dc:creator>
				<category><![CDATA[Technical Documentation]]></category>
		<category><![CDATA[Best Practices]]></category>
		<category><![CDATA[Communication]]></category>
		<category><![CDATA[How To]]></category>
		<category><![CDATA[Tips]]></category>
		<category><![CDATA[Training]]></category>
		<category><![CDATA[writing]]></category>

		<guid isPermaLink="false">http://www.wadeware.net/?p=1820</guid>
		<description><![CDATA[Having clearly defined requirements at the start of a project is extremely important. Requirements help establish and maintain a solid target throughout a project, help minimize wasted time and frustration, and can help ensure an organization maximizes its return on investment. This document contains suggested steps for discovering and defining business requirements.]]></description>
		<wfw:commentRss>http://www.wadeware.net/technical-documentation/how-to-discover-your-business-requirements/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>How to Interview a Subject Matter Expert</title>
		<link>http://www.wadeware.net/technical-documentation/how-to-interview-a-subject-matter-expert/</link>
		<comments>http://www.wadeware.net/technical-documentation/how-to-interview-a-subject-matter-expert/#comments</comments>
		<pubDate>Fri, 01 Apr 2011 00:10:56 +0000</pubDate>
		<dc:creator>Ryan Berg</dc:creator>
				<category><![CDATA[Technical Documentation]]></category>
		<category><![CDATA[How To]]></category>
		<category><![CDATA[project management]]></category>
		<category><![CDATA[Tips]]></category>
		<category><![CDATA[writing]]></category>

		<guid isPermaLink="false">http://www.wadeware.net/?p=1763</guid>
		<description><![CDATA[Gathering information for a writing assignment can be a very straightforward process. You are given (or pointed to) resources and collateral that provide you with product or project background, and you begin your investigation. Sometimes, however, when there just isn’t enough information to work with, you will likely need to interview a subject-matter expert (SME) [...]]]></description>
		<wfw:commentRss>http://www.wadeware.net/technical-documentation/how-to-interview-a-subject-matter-expert/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Haunted by Scope Creep</title>
		<link>http://www.wadeware.net/technical-documentation/haunted-by-scope-creep/</link>
		<comments>http://www.wadeware.net/technical-documentation/haunted-by-scope-creep/#comments</comments>
		<pubDate>Tue, 26 Oct 2010 22:48:01 +0000</pubDate>
		<dc:creator>John Cobb</dc:creator>
				<category><![CDATA[IT Courseware]]></category>
		<category><![CDATA[Technical Documentation]]></category>
		<category><![CDATA[editing]]></category>
		<category><![CDATA[Funny]]></category>
		<category><![CDATA[project management]]></category>
		<category><![CDATA[Rants and Raves]]></category>
		<category><![CDATA[Style Guides]]></category>
		<category><![CDATA[Tips]]></category>
		<category><![CDATA[writing]]></category>

		<guid isPermaLink="false">http://www.wadeware.net/?p=1468</guid>
		<description><![CDATA[Technical editor, John Cobb, shares his ghastly experience with projects involving Scope Creep.  Just in time for Halloween, the following blog post includes five tips on how to avoid scary technical documentation scope creep.]]></description>
		<wfw:commentRss>http://www.wadeware.net/technical-documentation/haunted-by-scope-creep/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Lync Server 2010 Tech Ed Presentations</title>
		<link>http://www.wadeware.net/technical-documentation/lync-server-2010-tech-ed-presentations/</link>
		<comments>http://www.wadeware.net/technical-documentation/lync-server-2010-tech-ed-presentations/#comments</comments>
		<pubDate>Mon, 13 Sep 2010 17:46:28 +0000</pubDate>
		<dc:creator>Thomas Foreman</dc:creator>
				<category><![CDATA[IT Courseware]]></category>
		<category><![CDATA[Technical Documentation]]></category>
		<category><![CDATA[CS 14]]></category>
		<category><![CDATA[CS 2010]]></category>
		<category><![CDATA[Lync 2010]]></category>
		<category><![CDATA[Lync Server 2010]]></category>
		<category><![CDATA[Lync Server 2010 (RC)]]></category>
		<category><![CDATA[Microsoft]]></category>
		<category><![CDATA[TechEd]]></category>

		<guid isPermaLink="false">http://www.wadeware.net/?p=1308</guid>
		<description><![CDATA[Learn a cool tip for getting all the TechEd presentation content from the TechEd blog.  A re-posted tip from the TechEd Team.]]></description>
		<wfw:commentRss>http://www.wadeware.net/technical-documentation/lync-server-2010-tech-ed-presentations/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Technical Writing + Editing = Effective Communications</title>
		<link>http://www.wadeware.net/technical-documentation/technical-writing-editing-effective-communications/</link>
		<comments>http://www.wadeware.net/technical-documentation/technical-writing-editing-effective-communications/#comments</comments>
		<pubDate>Thu, 19 Aug 2010 23:53:22 +0000</pubDate>
		<dc:creator>Steve Wacker</dc:creator>
				<category><![CDATA[Technical Documentation]]></category>
		<category><![CDATA[Communication]]></category>
		<category><![CDATA[Microsoft]]></category>
		<category><![CDATA[Tips]]></category>

		<guid isPermaLink="false">http://www.wadeware.net/?p=1243</guid>
		<description><![CDATA[Steve Wacker explains the importance of having effective communication skills with subject matter experts and clients when it comes to writing technical documentation.]]></description>
		<wfw:commentRss>http://www.wadeware.net/technical-documentation/technical-writing-editing-effective-communications/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Verbicide: Committing Grammatical Murder &amp; Other Verbal Crimes</title>
		<link>http://www.wadeware.net/technical-documentation/verbicide-committing-grammatical-murder-other-verbal-crimes/</link>
		<comments>http://www.wadeware.net/technical-documentation/verbicide-committing-grammatical-murder-other-verbal-crimes/#comments</comments>
		<pubDate>Wed, 03 Feb 2010 23:34:18 +0000</pubDate>
		<dc:creator>Steve Wacker</dc:creator>
				<category><![CDATA[Technical Documentation]]></category>
		<category><![CDATA[Funny]]></category>
		<category><![CDATA[Rants and Raves]]></category>

		<guid isPermaLink="false">http://www.wadeware.net/?p=909</guid>
		<description><![CDATA[This post takes a poke or two at those who maim the language through verbicide as well as those who worry about how language evolves. It also meanders a bit into the world of puns and malapropisms but still manages to find its way home. ]]></description>
		<wfw:commentRss>http://www.wadeware.net/technical-documentation/verbicide-committing-grammatical-murder-other-verbal-crimes/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>5 Good Reasons to Use a Style Guide</title>
		<link>http://www.wadeware.net/technical-documentation/5-good-reasons-to-use-a-style-guide/</link>
		<comments>http://www.wadeware.net/technical-documentation/5-good-reasons-to-use-a-style-guide/#comments</comments>
		<pubDate>Tue, 24 Nov 2009 17:20:46 +0000</pubDate>
		<dc:creator>Steve Wacker</dc:creator>
				<category><![CDATA[Technical Documentation]]></category>
		<category><![CDATA[Best Practices]]></category>
		<category><![CDATA[Style Guides]]></category>

		<guid isPermaLink="false">http://www.wadeware.net/?p=774</guid>
		<description><![CDATA[Steve Wacker, a technical documentation writer and editor at Wadeware, shares 5 good reasons to use a style guide when developing technical content.]]></description>
		<wfw:commentRss>http://www.wadeware.net/technical-documentation/5-good-reasons-to-use-a-style-guide/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

