<?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; Style Guides</title>
	<atom:link href="http://www.wadeware.net/tag/style-guides/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>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>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>

