<?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; Best Practices</title>
	<atom:link href="http://www.wadeware.net/tag/best-practices/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.wadeware.net</link>
	<description>IT Consulting + Training &#38; Support</description>
	<lastBuildDate>Thu, 26 Aug 2010 19:50:45 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
		<item>
		<title>5 Instructional Design Best Practices</title>
		<link>http://www.wadeware.net/courseware/5-instructional-design-best-practices/</link>
		<comments>http://www.wadeware.net/courseware/5-instructional-design-best-practices/#comments</comments>
		<pubDate>Fri, 29 Jan 2010 18:40:02 +0000</pubDate>
		<dc:creator>Dennis Rea</dc:creator>
				<category><![CDATA[Courseware]]></category>
		<category><![CDATA[Best Practices]]></category>
		<category><![CDATA[How To]]></category>

		<guid isPermaLink="false">http://www.wadeware.net/?p=854</guid>
		<description><![CDATA[A common mistake in courseware design is trying to force students to learn too much too soon. Keep them engaged throughout your learning sessions by following these instructional design best practices.]]></description>
		<wfw:commentRss>http://www.wadeware.net/courseware/5-instructional-design-best-practices/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>
