<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: Long Help Topics: A Help Author&#8217;s Crime against Humanity</title>
	<atom:link href="http://www.gryphonmountain.net/2008/09/long-help-topics-a-help-authors-crime-against-humanity/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.gryphonmountain.net/2008/09/long-help-topics-a-help-authors-crime-against-humanity/</link>
	<description>Technical Communication and Other Writing Topics (by Ben Minson)</description>
	<lastBuildDate>Thu, 11 Mar 2010 13:12:35 -0600</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Leaning Towards Longer Topics and Shorter TOCs &#124; I'd Rather Be Writing - Tom Johnson</title>
		<link>http://www.gryphonmountain.net/2008/09/long-help-topics-a-help-authors-crime-against-humanity/comment-page-1/#comment-3806</link>
		<dc:creator>Leaning Towards Longer Topics and Shorter TOCs &#124; I'd Rather Be Writing - Tom Johnson</dc:creator>
		<pubDate>Tue, 23 Sep 2008 05:41:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.gryphonmountain.net/?p=128#comment-3806</guid>
		<description>[...] My colleague Ben Minson, however, raises an important objection to long topics. He says, In reality, people don’t want long topics. They want to think that procedures are short and simple. Long topics intimidate people and make them reluctant to consult the documentation in the future. (&#8221;Long Topics: A Help Author&#8217;s Crime Against Humanity&#8220;) [...]</description>
		<content:encoded><![CDATA[<p>[...] My colleague Ben Minson, however, raises an important objection to long topics. He says, In reality, people don’t want long topics. They want to think that procedures are short and simple. Long topics intimidate people and make them reluctant to consult the documentation in the future. (&#8221;Long Topics: A Help Author&#8217;s Crime Against Humanity&#8220;) [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ben</title>
		<link>http://www.gryphonmountain.net/2008/09/long-help-topics-a-help-authors-crime-against-humanity/comment-page-1/#comment-3554</link>
		<dc:creator>Ben</dc:creator>
		<pubDate>Wed, 17 Sep 2008 23:00:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.gryphonmountain.net/?p=128#comment-3554</guid>
		<description>I thought of the bloated TOC problem. With MS products, I never browse the TOC because I can rarely find what I want. (Maybe that means I need to rethink having the TOC as the default display in the left pane of my help systems...) I admit that I&#039;m a member of the Google generation, and I use the search to locate what I want.</description>
		<content:encoded><![CDATA[<p>I thought of the bloated TOC problem. With MS products, I never browse the TOC because I can rarely find what I want. (Maybe that means I need to rethink having the TOC as the default display in the left pane of my help systems&#8230;) I admit that I&#8217;m a member of the Google generation, and I use the search to locate what I want.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tom Johnson</title>
		<link>http://www.gryphonmountain.net/2008/09/long-help-topics-a-help-authors-crime-against-humanity/comment-page-1/#comment-3507</link>
		<dc:creator>Tom Johnson</dc:creator>
		<pubDate>Tue, 16 Sep 2008 20:22:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.gryphonmountain.net/?p=128#comment-3507</guid>
		<description>I think Microsoft&#039;s help in Word and SharePoint (and probably others) has trended toward longer topics, with a quick jump menu at the top. 

It&#039;s nice to break up a topic into a lot of little subtopics (each separate files), but then you end up with a bloated table of contents that makes the app look  a lot more sophisticated than it really is.</description>
		<content:encoded><![CDATA[<p>I think Microsoft&#8217;s help in Word and SharePoint (and probably others) has trended toward longer topics, with a quick jump menu at the top. </p>
<p>It&#8217;s nice to break up a topic into a lot of little subtopics (each separate files), but then you end up with a bloated table of contents that makes the app look  a lot more sophisticated than it really is.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
