<?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/"
	xmlns:series="http://unfoldingneurons.com/"
	>

<channel>
	<title>Every Page is Page One</title>
	<atom:link href="http://everypageispageone.com/feed/" rel="self" type="application/rss+xml" />
	<link>http://everypageispageone.com</link>
	<description>Readers can enter anywhere. Is your content ready to receive them?</description>
	<lastBuildDate>Fri, 11 May 2012 20:13:29 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
		<item>
		<title>The Design Implications of Tool Choices</title>
		<link>http://everypageispageone.com/2012/05/11/the-design-implications-of-tool-choices/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=the-design-implications-of-tool-choices</link>
		<comments>http://everypageispageone.com/2012/05/11/the-design-implications-of-tool-choices/#comments</comments>
		<pubDate>Fri, 11 May 2012 20:13:29 +0000</pubDate>
		<dc:creator>Mark Baker</dc:creator>
				<category><![CDATA[Every Page is Page One]]></category>
		<category><![CDATA[Process and Politics]]></category>
		<category><![CDATA[Writer vs. Reader]]></category>
		<category><![CDATA[AuthorIt]]></category>
		<category><![CDATA[books]]></category>
		<category><![CDATA[design]]></category>
		<category><![CDATA[DITA]]></category>
		<category><![CDATA[FrameMaker]]></category>
		<category><![CDATA[Frankenbooks]]></category>
		<category><![CDATA[JoAnn Hackos]]></category>
		<category><![CDATA[linking]]></category>
		<category><![CDATA[SPFE]]></category>
		<category><![CDATA[structured writing]]></category>
		<category><![CDATA[tools]]></category>
		<category><![CDATA[topics]]></category>

		<guid isPermaLink="false">http://everypageispageone.com/?p=859</guid>
		<description><![CDATA[Every documentation tool has a built in information design bias. When you choose a tool, be it FrameMaker, DITA, AuthorIt, a WIKI, or SPFE, you are implicitly choosing an approach to information design. If you don&#8217;t understand and accept the design implications of your tool choice, as many people do not, you are setting yourself [...]]]></description>
		<wfw:commentRss>http://everypageispageone.com/2012/05/11/the-design-implications-of-tool-choices/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>I am a Content Strategist</title>
		<link>http://everypageispageone.com/2012/05/04/i-am-a-content-strategist/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=i-am-a-content-strategist</link>
		<comments>http://everypageispageone.com/2012/05/04/i-am-a-content-strategist/#comments</comments>
		<pubDate>Fri, 04 May 2012 21:26:32 +0000</pubDate>
		<dc:creator>Mark Baker</dc:creator>
				<category><![CDATA[Process and Politics]]></category>
		<category><![CDATA[Show me the Money]]></category>

		<guid isPermaLink="false">http://everypageispageone.com/?p=844</guid>
		<description><![CDATA[A couple of weeks ago, I wrote a post asking Am I a Content Strategist? In response, Sarah O&#8217;Keefe tweeted &#8220;If you&#8217;re not, then nobody is.&#8221; &#8212; which is good enough for me. The question wasn&#8217;t really about me, of course. It was a question about the nature of content strategy. Was content strategy a field (in [...]]]></description>
		<wfw:commentRss>http://everypageispageone.com/2012/05/04/i-am-a-content-strategist/feed/</wfw:commentRss>
		<slash:comments>8</slash:comments>
		</item>
		<item>
		<title>Am I a Content Strategist?</title>
		<link>http://everypageispageone.com/2012/04/13/am-i-a-content-strategist/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=am-i-a-content-strategist</link>
		<comments>http://everypageispageone.com/2012/04/13/am-i-a-content-strategist/#comments</comments>
		<pubDate>Fri, 13 Apr 2012 18:19:58 +0000</pubDate>
		<dc:creator>Mark Baker</dc:creator>
				<category><![CDATA[Every Page is Page One]]></category>
		<category><![CDATA[Process and Politics]]></category>
		<category><![CDATA[Show me the Money]]></category>
		<category><![CDATA[Barbara Saunders]]></category>
		<category><![CDATA[content management]]></category>
		<category><![CDATA[content strategist]]></category>
		<category><![CDATA[content strategy]]></category>
		<category><![CDATA[David Weinberger]]></category>
		<category><![CDATA[hierarchy]]></category>
		<category><![CDATA[job titles]]></category>
		<category><![CDATA[Scott Able]]></category>
		<category><![CDATA[technical writer]]></category>

		<guid isPermaLink="false">http://everypageispageone.com/?p=826</guid>
		<description><![CDATA[I&#8217;m a fan of emerging technology, and generally tolerant of emerging terminology, but when it comes to job titles I tend to the view that if it was not mentioned in the Domesday Book, it isn&#8217;t a real job. I have, on diverse occasions, decried attempts to replace the title &#8220;technical writer&#8221; with something else, [...]]]></description>
		<wfw:commentRss>http://everypageispageone.com/2012/04/13/am-i-a-content-strategist/feed/</wfw:commentRss>
		<slash:comments>8</slash:comments>
		</item>
		<item>
		<title>From Publications to Conversations</title>
		<link>http://everypageispageone.com/2012/04/02/from-publications-to-conversations/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=from-publications-to-conversations</link>
		<comments>http://everypageispageone.com/2012/04/02/from-publications-to-conversations/#comments</comments>
		<pubDate>Mon, 02 Apr 2012 17:35:39 +0000</pubDate>
		<dc:creator>Mark Baker</dc:creator>
				<category><![CDATA[Process and Politics]]></category>

		<guid isPermaLink="false">http://everypageispageone.com/?p=811</guid>
		<description><![CDATA[I am grateful to Connie Giordano for the invitation to contribute to techwr-l&#8217;s Integrated Technical Communications series. My contribution, It&#8217;s time for a New Doctrine of Technical Communications, appears today. Connie&#8217;s request was prompted by a number of comments I have made recently on the future of tech pubs, but it forced me to think a little more deeply [...]]]></description>
		<wfw:commentRss>http://everypageispageone.com/2012/04/02/from-publications-to-conversations/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Findability vs. Searchability</title>
		<link>http://everypageispageone.com/2012/03/21/findability-vs-searchability/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=findability-vs-searchability</link>
		<comments>http://everypageispageone.com/2012/03/21/findability-vs-searchability/#comments</comments>
		<pubDate>Wed, 21 Mar 2012 20:19:56 +0000</pubDate>
		<dc:creator>Mark Baker</dc:creator>
				<category><![CDATA[Hide and Seek]]></category>
		<category><![CDATA[books]]></category>
		<category><![CDATA[find]]></category>
		<category><![CDATA[findability]]></category>
		<category><![CDATA[Google]]></category>
		<category><![CDATA[index]]></category>
		<category><![CDATA[readers]]></category>
		<category><![CDATA[search]]></category>
		<category><![CDATA[serchability]]></category>
		<category><![CDATA[taxonomy]]></category>
		<category><![CDATA[TOC]]></category>
		<category><![CDATA[web]]></category>

		<guid isPermaLink="false">http://everypageispageone.com/?p=799</guid>
		<description><![CDATA[I argued in Too Big to Browse; Too Small to Search, that search works best when it has a large amount of content to work with. But it occurs to me that there is a really important caveat to be made, which I can best express as the difference between findability and searchability. The distinction [...]]]></description>
		<wfw:commentRss>http://everypageispageone.com/2012/03/21/findability-vs-searchability/feed/</wfw:commentRss>
		<slash:comments>21</slash:comments>
		</item>
		<item>
		<title>Interest is Fundamental to Communication</title>
		<link>http://everypageispageone.com/2012/03/13/interest-is-fundamental-to-communication/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=interest-is-fundamental-to-communication</link>
		<comments>http://everypageispageone.com/2012/03/13/interest-is-fundamental-to-communication/#comments</comments>
		<pubDate>Tue, 13 Mar 2012 21:07:46 +0000</pubDate>
		<dc:creator>Mark Baker</dc:creator>
				<category><![CDATA[Process and Politics]]></category>
		<category><![CDATA[Writer vs. Reader]]></category>
		<category><![CDATA[engineers]]></category>
		<category><![CDATA[interests]]></category>
		<category><![CDATA[readers]]></category>
		<category><![CDATA[subjects]]></category>
		<category><![CDATA[writers]]></category>

		<guid isPermaLink="false">http://everypageispageone.com/?p=790</guid>
		<description><![CDATA[The Web continues to invent new places for tech writers to rehash old arguments. Recently I have been seeing a number of reiterations of the old debate about technical knowledge vs. writing skill on various LinkedIn forums, and apparently Techwr-l has recently been debating yet again whether it is easier to teach tech to a [...]]]></description>
		<wfw:commentRss>http://everypageispageone.com/2012/03/13/interest-is-fundamental-to-communication/feed/</wfw:commentRss>
		<slash:comments>5</slash:comments>
		</item>
		<item>
		<title>Too Big to Browse; Too Small to Search</title>
		<link>http://everypageispageone.com/2012/03/03/too-big-to-browse-too-small-to-search/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=too-big-to-browse-too-small-to-search</link>
		<comments>http://everypageispageone.com/2012/03/03/too-big-to-browse-too-small-to-search/#comments</comments>
		<pubDate>Sat, 03 Mar 2012 18:49:06 +0000</pubDate>
		<dc:creator>Mark Baker</dc:creator>
				<category><![CDATA[Every Page is Page One]]></category>
		<category><![CDATA[Hide and Seek]]></category>
		<category><![CDATA[Objects vs. Chunks]]></category>
		<category><![CDATA[books]]></category>
		<category><![CDATA[findability]]></category>
		<category><![CDATA[Google]]></category>
		<category><![CDATA[hierarchy]]></category>
		<category><![CDATA[information]]></category>
		<category><![CDATA[Internet]]></category>
		<category><![CDATA[readers]]></category>
		<category><![CDATA[search]]></category>
		<category><![CDATA[topics]]></category>

		<guid isPermaLink="false">http://everypageispageone.com/?p=778</guid>
		<description><![CDATA[Findability continues to be the bete noire of technical communication. This may be a parallax error, but it seems that findability is more of a problem in technical communication than in other fields. The reason, I suspect, is that many technical documentation suites are too big to browse but too small to search. I have [...]]]></description>
		<wfw:commentRss>http://everypageispageone.com/2012/03/03/too-big-to-browse-too-small-to-search/feed/</wfw:commentRss>
		<slash:comments>7</slash:comments>
		</item>
		<item>
		<title>Frankenbooks Must Die: A Rant</title>
		<link>http://everypageispageone.com/2012/02/24/frankenbooks-must-die-a-rant/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=frankenbooks-must-die-a-rant</link>
		<comments>http://everypageispageone.com/2012/02/24/frankenbooks-must-die-a-rant/#comments</comments>
		<pubDate>Fri, 24 Feb 2012 21:48:00 +0000</pubDate>
		<dc:creator>Mark Baker</dc:creator>
				<category><![CDATA[Every Page is Page One]]></category>
		<category><![CDATA[Objects vs. Chunks]]></category>
		<category><![CDATA[Writer vs. Reader]]></category>
		<category><![CDATA[books]]></category>
		<category><![CDATA[chunking]]></category>
		<category><![CDATA[DITA]]></category>
		<category><![CDATA[FrameMaker]]></category>
		<category><![CDATA[Frankenbooks]]></category>
		<category><![CDATA[hierarchy]]></category>
		<category><![CDATA[information architect]]></category>
		<category><![CDATA[query]]></category>
		<category><![CDATA[rant]]></category>
		<category><![CDATA[readers]]></category>
		<category><![CDATA[Sarah Maddox]]></category>
		<category><![CDATA[standalone]]></category>
		<category><![CDATA[the Web]]></category>
		<category><![CDATA[topics]]></category>

		<guid isPermaLink="false">http://everypageispageone.com/?p=760</guid>
		<description><![CDATA[I was astonished at Sarah Maddox&#8217;s statement, in her guest post Why don’t technical writers use wikis — or do they? on I&#8217;d Rather be Writing, that wikis are not good at topic-based writing. Huh? Wikis are all about topic-based writing. In fact, it is the only type of writing they really support. What&#8217;s wrong here? [...]]]></description>
		<wfw:commentRss>http://everypageispageone.com/2012/02/24/frankenbooks-must-die-a-rant/feed/</wfw:commentRss>
		<slash:comments>9</slash:comments>
		</item>
		<item>
		<title>The Segmentation of Tech Comm</title>
		<link>http://everypageispageone.com/2012/02/16/the-segmentation-of-tech-comm/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=the-segmentation-of-tech-comm</link>
		<comments>http://everypageispageone.com/2012/02/16/the-segmentation-of-tech-comm/#comments</comments>
		<pubDate>Thu, 16 Feb 2012 20:16:18 +0000</pubDate>
		<dc:creator>Mark Baker</dc:creator>
				<category><![CDATA[Process and Politics]]></category>
		<category><![CDATA[Show me the Money]]></category>
		<category><![CDATA[channels]]></category>
		<category><![CDATA[DITA]]></category>
		<category><![CDATA[FrameMaker]]></category>
		<category><![CDATA[Jack Molisani]]></category>
		<category><![CDATA[qualifications]]></category>
		<category><![CDATA[Sarah O'Keefe]]></category>
		<category><![CDATA[scope]]></category>
		<category><![CDATA[Scott Abel]]></category>
		<category><![CDATA[segmentation]]></category>
		<category><![CDATA[SPFE]]></category>
		<category><![CDATA[tools]]></category>
		<category><![CDATA[Val Swisher]]></category>
		<category><![CDATA[wiki]]></category>

		<guid isPermaLink="false">http://everypageispageone.com/?p=738</guid>
		<description><![CDATA[I was flattered that my post Technical Communication is not a Commodity was used as a catalyst for Scott Abel&#8217;s discussion with Val Swisher, Jack Molisani and Sarah O&#8217;Keefe on The Changing Face of Technical Communications, What&#8217;s Next? I had a fair amount to say in the comment stream that followed to defend my assertion that [...]]]></description>
		<wfw:commentRss>http://everypageispageone.com/2012/02/16/the-segmentation-of-tech-comm/feed/</wfw:commentRss>
		<slash:comments>15</slash:comments>
		</item>
		<item>
		<title>The Web Does Minimalism</title>
		<link>http://everypageispageone.com/2012/02/06/the-web-does-minimalism/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=the-web-does-minimalism</link>
		<comments>http://everypageispageone.com/2012/02/06/the-web-does-minimalism/#comments</comments>
		<pubDate>Mon, 06 Feb 2012 20:48:09 +0000</pubDate>
		<dc:creator>Mark Baker</dc:creator>
				<category><![CDATA[Every Page is Page One]]></category>
		<category><![CDATA[Hide and Seek]]></category>
		<category><![CDATA[David Weinberger]]></category>
		<category><![CDATA[Google]]></category>
		<category><![CDATA[Minimalism]]></category>
		<category><![CDATA[the Web]]></category>

		<guid isPermaLink="false">http://everypageispageone.com/?p=733</guid>
		<description><![CDATA[It struck me today that the Web does Minimalism. Not only does it do it, it does it naturally, and it does it well. Consider: Here&#8217;s a common listing of the principle tenants of minimalism (borrowed from http://www.ryerson.ca/~ipederse/Minimalism.htm via Google): Take An Action-Oriented Approach Aim for Guided Exploration Position the Documentation in the Task Domain [...]]]></description>
		<wfw:commentRss>http://everypageispageone.com/2012/02/06/the-web-does-minimalism/feed/</wfw:commentRss>
		<slash:comments>9</slash:comments>
		</item>
	</channel>
</rss>

