<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" media="screen" href="/~d/styles/rss2full.xsl"?><?xml-stylesheet type="text/css" media="screen" href="http://feeds.feedburner.com/~d/styles/itemcontent.css"?><rss 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:feedburner="http://rssnamespace.org/feedburner/ext/1.0" version="2.0">

<channel>
	<title>Cherryleaf Technical Authors Blog</title>
	
	<link>http://www.cherryleaf.com/blog</link>
	<description>We write that missing information your users really need. Telephone +44 1784 258672</description>
	<pubDate>Fri, 03 Jul 2009 14:20:32 +0000</pubDate>
	<generator>http://wordpress.org/?v=abc</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" href="www.cherryleaf.com/atom.xml" type="application/rss+xml" /><feedburner:browserFriendly>This is an XML content feed. It is intended to be viewed in a newsreader or syndicated to another site.</feedburner:browserFriendly><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://pubsubhubbub.appspot.com" /><item>
		<title>Trust is the new critical currency in the connected age</title>
		<link>http://feedproxy.google.com/~r/CherryleafTechnicalAuthorsBlog/~3/qOdC3YXNeio/</link>
		<comments>http://www.cherryleaf.com/blog/2009/07/trust-is-the-new-critical-currency-in-the-connected-age/#comments</comments>
		<pubDate>Fri, 03 Jul 2009 14:15:59 +0000</pubDate>
		<dc:creator>ellis</dc:creator>
		
		<category><![CDATA[trends]]></category>

		<category><![CDATA[trust]]></category>

		<category><![CDATA[technical documentation]]></category>

		<guid isPermaLink="false">http://www.cherryleaf.com/blog/?p=717</guid>
		
			<content:encoded><![CDATA[Trust is the new critical currency in the connected age.&#8221;
This is a Twitter post by Scott Berg, Director of HP Global Digital Strategy. 
Assuming technical communicators produce highly...<br/>
<br/>
[[ For the full article, see http://www.cherryleaf.com/blog.htm]]]]></content:encoded>
			<wfw:commentRss>http://www.cherryleaf.com/blog/2009/07/trust-is-the-new-critical-currency-in-the-connected-age/feed/</wfw:commentRss>
		<feedburner:origLink>http://www.cherryleaf.com/blog/2009/07/trust-is-the-new-critical-currency-in-the-connected-age/</feedburner:origLink></item>
		<item>
		<title>Saving content from oblivion: If it’s not online, it’s invisible.</title>
		<link>http://feedproxy.google.com/~r/CherryleafTechnicalAuthorsBlog/~3/oLpRmTFQrQY/</link>
		<comments>http://www.cherryleaf.com/blog/2009/07/saving-content-from-oblivion-if-its-not-online-its-invisible/#comments</comments>
		<pubDate>Fri, 03 Jul 2009 14:10:11 +0000</pubDate>
		<dc:creator>ellis</dc:creator>
		
		<category><![CDATA[technical authors]]></category>

		<category><![CDATA[trends]]></category>

		<category><![CDATA[research]]></category>

		<guid isPermaLink="false">http://www.cherryleaf.com/blog/?p=714</guid>
		
			<content:encoded><![CDATA[Oxford University Press&#8217;s Tim Barton, in an article on the Google Book Settlement, states:
What once seemed at least debatable has now become irrefutable: If it&#8217;s not online, it&#8217;s...<br/>
<br/>
[[ For the full article, see http://www.cherryleaf.com/blog.htm]]]]></content:encoded>
			<wfw:commentRss>http://www.cherryleaf.com/blog/2009/07/saving-content-from-oblivion-if-its-not-online-its-invisible/feed/</wfw:commentRss>
		<feedburner:origLink>http://www.cherryleaf.com/blog/2009/07/saving-content-from-oblivion-if-its-not-online-its-invisible/</feedburner:origLink></item>
		<item>
		<title>Ten key issues for CEOs of software companies</title>
		<link>http://feedproxy.google.com/~r/CherryleafTechnicalAuthorsBlog/~3/TB_Js_46dLA/</link>
		<comments>http://www.cherryleaf.com/blog/2009/07/ten-key-issues-for-ceos-of-software-companies/#comments</comments>
		<pubDate>Fri, 03 Jul 2009 13:49:36 +0000</pubDate>
		<dc:creator>ellis</dc:creator>
		
		<category><![CDATA[Technical Communication]]></category>

		<category><![CDATA[content management]]></category>

		<category><![CDATA[downturn]]></category>

		<category><![CDATA[management]]></category>

		<category><![CDATA[technical documentation]]></category>

		<category><![CDATA[trends]]></category>

		<category><![CDATA[xml]]></category>

		<category><![CDATA[meetings]]></category>

		<guid isPermaLink="false">http://www.cherryleaf.com/blog/?p=701</guid>
		
			<content:encoded><![CDATA[At Intellect (the trade association for UK technology companies) yesterday, there was a meeting looking at how UK software companies are faring in this current economic climate. At this event,...<br/>
<br/>
[[ For the full article, see http://www.cherryleaf.com/blog.htm]]]]></content:encoded>
			<wfw:commentRss>http://www.cherryleaf.com/blog/2009/07/ten-key-issues-for-ceos-of-software-companies/feed/</wfw:commentRss>
		<feedburner:origLink>http://www.cherryleaf.com/blog/2009/07/ten-key-issues-for-ceos-of-software-companies/</feedburner:origLink></item>
		<item>
		<title>Lessons for technical communicators from the telecommunications sector</title>
		<link>http://feedproxy.google.com/~r/CherryleafTechnicalAuthorsBlog/~3/2OF-Lu4TQHE/</link>
		<comments>http://www.cherryleaf.com/blog/2009/06/lessons-for-technical-communicators-from-the-telecommunications-sector/#comments</comments>
		<pubDate>Mon, 29 Jun 2009 16:03:25 +0000</pubDate>
		<dc:creator>ellis</dc:creator>
		
		<category><![CDATA[Technical Communication]]></category>

		<category><![CDATA[Web 2.0]]></category>

		<category><![CDATA[management]]></category>

		<category><![CDATA[marketing]]></category>

		<category><![CDATA[technical author]]></category>

		<category><![CDATA[technical publications; technical author]]></category>

		<category><![CDATA[trends]]></category>

		<category><![CDATA[user assistance]]></category>

		<category><![CDATA[content management]]></category>

		<category><![CDATA[documentation]]></category>

		<category><![CDATA[documentation managers]]></category>

		<guid isPermaLink="false">http://www.cherryleaf.com/blog/?p=690</guid>
		
			<content:encoded><![CDATA[It&#8217;s often useful to look at the economic and technological pressures in other industries, to see if the trends emerging there are relevant to the technical communications/publications sector....<br/>
<br/>
[[ For the full article, see http://www.cherryleaf.com/blog.htm]]]]></content:encoded>
			<wfw:commentRss>http://www.cherryleaf.com/blog/2009/06/lessons-for-technical-communicators-from-the-telecommunications-sector/feed/</wfw:commentRss>
		<feedburner:origLink>http://www.cherryleaf.com/blog/2009/06/lessons-for-technical-communicators-from-the-telecommunications-sector/</feedburner:origLink></item>
		<item>
		<title>If your Technical Publications department was a business</title>
		<link>http://feedproxy.google.com/~r/CherryleafTechnicalAuthorsBlog/~3/2eBuPlnizSo/</link>
		<comments>http://www.cherryleaf.com/blog/2009/06/if-your-technical-publications-department-was-a-business/#comments</comments>
		<pubDate>Mon, 29 Jun 2009 15:32:54 +0000</pubDate>
		<dc:creator>ellis</dc:creator>
		
		<category><![CDATA[management]]></category>

		<category><![CDATA[marketing]]></category>

		<category><![CDATA[project management]]></category>

		<category><![CDATA[technical documentation]]></category>

		<guid isPermaLink="false">http://www.cherryleaf.com/blog/?p=683</guid>
		
			<content:encoded><![CDATA[Sometimes it&#8217;s good for managers to look at a department in a slightly different way from normal. What, for example, if the Technical Publications department was a business? If a business...<br/>
<br/>
[[ For the full article, see http://www.cherryleaf.com/blog.htm]]]]></content:encoded>
			<wfw:commentRss>http://www.cherryleaf.com/blog/2009/06/if-your-technical-publications-department-was-a-business/feed/</wfw:commentRss>
		<feedburner:origLink>http://www.cherryleaf.com/blog/2009/06/if-your-technical-publications-department-was-a-business/</feedburner:origLink></item>
		<item>
		<title>“Push me, Pull me” dilemma for technical authors</title>
		<link>http://feedproxy.google.com/~r/CherryleafTechnicalAuthorsBlog/~3/sKk1GcpW4qI/</link>
		<comments>http://www.cherryleaf.com/blog/2009/06/push-me-pull-me-dilemma-for-technical-authors/#comments</comments>
		<pubDate>Sun, 28 Jun 2009 08:44:48 +0000</pubDate>
		<dc:creator>ellis</dc:creator>
		
		<category><![CDATA[Technical Communication]]></category>

		<category><![CDATA[collaborative authoring]]></category>

		<category><![CDATA[management]]></category>

		<category><![CDATA[online communities]]></category>

		<category><![CDATA[technical authors]]></category>

		<category><![CDATA[technical communicators]]></category>

		<category><![CDATA[trends]]></category>

		<category><![CDATA[user assistance]]></category>

		<category><![CDATA[user generated content]]></category>

		<category><![CDATA[documentation]]></category>

		<guid isPermaLink="false">http://www.cherryleaf.com/blog/?p=667</guid>
		
			<content:encoded><![CDATA[There are a number of posts on various Blogs, at the moment, concerning documents as conversation and moving beyond the traditional manual. Some of the comments suggest implicitly  that technical...<br/>
<br/>
[[ For the full article, see http://www.cherryleaf.com/blog.htm]]]]></content:encoded>
			<wfw:commentRss>http://www.cherryleaf.com/blog/2009/06/push-me-pull-me-dilemma-for-technical-authors/feed/</wfw:commentRss>
		<feedburner:origLink>http://www.cherryleaf.com/blog/2009/06/push-me-pull-me-dilemma-for-technical-authors/</feedburner:origLink></item>
		<item>
		<title>Which model of communication will technical communicators employ in the future?</title>
		<link>http://feedproxy.google.com/~r/CherryleafTechnicalAuthorsBlog/~3/51UIYYr-Pu4/</link>
		<comments>http://www.cherryleaf.com/blog/2009/06/what-model-of-communication-will-technical-communicators-employ-in-the-future/#comments</comments>
		<pubDate>Thu, 25 Jun 2009 18:17:43 +0000</pubDate>
		<dc:creator>ellis</dc:creator>
		
		<category><![CDATA[Technical Communication]]></category>

		<category><![CDATA[technical communicators]]></category>

		<category><![CDATA[technical documentation]]></category>

		<category><![CDATA[trends]]></category>

		<category><![CDATA[usability]]></category>

		<category><![CDATA[user generated content]]></category>

		<category><![CDATA[collaborative authoring]]></category>

		<category><![CDATA[technical authors]]></category>

		<category><![CDATA[xml]]></category>

		<guid isPermaLink="false">http://www.cherryleaf.com/blog/?p=646</guid>
		
			<content:encoded><![CDATA[About 44 minutes into his presentation, Michael Wesch talked about network size and the effect it traditionally has on the ways teachers communicate information to students. He said as the audience...<br/>
<br/>
[[ For the full article, see http://www.cherryleaf.com/blog.htm]]]]></content:encoded>
			<wfw:commentRss>http://www.cherryleaf.com/blog/2009/06/what-model-of-communication-will-technical-communicators-employ-in-the-future/feed/</wfw:commentRss>
		<feedburner:origLink>http://www.cherryleaf.com/blog/2009/06/what-model-of-communication-will-technical-communicators-employ-in-the-future/</feedburner:origLink></item>
		<item>
		<title>Is the future of education also the future of technical communication?</title>
		<link>http://feedproxy.google.com/~r/CherryleafTechnicalAuthorsBlog/~3/31CJJFHAgTI/</link>
		<comments>http://www.cherryleaf.com/blog/2009/06/is-the-future-of-education-also-the-future-of-technical-communication/#comments</comments>
		<pubDate>Thu, 25 Jun 2009 16:24:29 +0000</pubDate>
		<dc:creator>ellis</dc:creator>
		
		<category><![CDATA[Technical Communication]]></category>

		<category><![CDATA[documentation]]></category>

		<category><![CDATA[technology]]></category>

		<category><![CDATA[trends]]></category>

		<category><![CDATA[user assistance]]></category>

		<category><![CDATA[collaborative authoring]]></category>

		<category><![CDATA[research]]></category>

		<guid isPermaLink="false">http://www.cherryleaf.com/blog/?p=638</guid>
		
			<content:encoded><![CDATA[I stumbled across another great video of Michael Wesch talking about the issues facing educationalists.  Many of the problems they face are the same as those faced by people involved in producing...<br/>
<br/>
[[ For the full article, see http://www.cherryleaf.com/blog.htm]]]]></content:encoded>
			<wfw:commentRss>http://www.cherryleaf.com/blog/2009/06/is-the-future-of-education-also-the-future-of-technical-communication/feed/</wfw:commentRss>
		<feedburner:origLink>http://www.cherryleaf.com/blog/2009/06/is-the-future-of-education-also-the-future-of-technical-communication/</feedburner:origLink></item>
		<item>
		<title>Why pay 2.5 times the national average salary for a technical author?</title>
		<link>http://feedproxy.google.com/~r/CherryleafTechnicalAuthorsBlog/~3/8-mggP8_32Q/</link>
		<comments>http://www.cherryleaf.com/blog/2009/06/why-pay-25-times-the-national-average-salary-for-a-technical-author/#comments</comments>
		<pubDate>Mon, 22 Jun 2009 09:09:58 +0000</pubDate>
		<dc:creator>ellis</dc:creator>
		
		<category><![CDATA[Technical Communication]]></category>

		<category><![CDATA[Vacancies]]></category>

		<category><![CDATA[job]]></category>

		<category><![CDATA[jobs]]></category>

		<category><![CDATA[recruitment]]></category>

		<guid isPermaLink="false">http://www.cherryleaf.com/blog/?p=632</guid>
		
			<content:encoded><![CDATA[We&#8217;ve just posted up a vacancy for a lead technical author in Switzerland with a salary of circa £64,000 ($105,744) - around two and a half times the average salary in the UK. So why would...<br/>
<br/>
[[ For the full article, see http://www.cherryleaf.com/blog.htm]]]]></content:encoded>
			<wfw:commentRss>http://www.cherryleaf.com/blog/2009/06/why-pay-25-times-the-national-average-salary-for-a-technical-author/feed/</wfw:commentRss>
		<feedburner:origLink>http://www.cherryleaf.com/blog/2009/06/why-pay-25-times-the-national-average-salary-for-a-technical-author/</feedburner:origLink></item>
		<item>
		<title>Video plug-in test</title>
		<link>http://feedproxy.google.com/~r/CherryleafTechnicalAuthorsBlog/~3/wquPHREYVW8/</link>
		<comments>http://www.cherryleaf.com/blog/2009/06/test/#comments</comments>
		<pubDate>Sat, 20 Jun 2009 06:43:09 +0000</pubDate>
		<dc:creator>Administrator</dc:creator>
		
		<category><![CDATA[Cherryleaf]]></category>

		<category><![CDATA[technical author]]></category>

		<guid isPermaLink="false">http://www.cherryleaf.com/blog/?p=627</guid>
		
			<content:encoded><![CDATA[<br/>
<br/>
[[ For the full article, see http://www.cherryleaf.com/blog.htm]]]]></content:encoded>
			<wfw:commentRss>http://www.cherryleaf.com/blog/2009/06/test/feed/</wfw:commentRss>
		<feedburner:origLink>http://www.cherryleaf.com/blog/2009/06/test/</feedburner:origLink></item>
	<item><title>Cherryleaf to host mentoring meetings for Documentation Managers Cherryleaf Technical Authors Cherryleaf Technical Authors Blog [del.icio.us]</title><link>http://feedproxy.google.com/~r/CherryleafTechnicalAuthorsBlog/~3/hRPXom6ijj0/</link><category>documentation technical-author technical-communicators</category><dc:creator>ellispratt</dc:creator><pubDate>Mon, 30 Mar 2009 06:34:41 PDT</pubDate><guid isPermaLink="false">http://www.cherryleaf.com/blog/2009/03/facilitated-mentoring-meetings-for-documentation-managers/</guid><description>Cherryleaf will be hosting, half-day peer group meetings for documentation managers and leaders. These afternoon meetings will be held initially on a quarterly basis in Russell Square, London, under the Chatham House Rule basis of confidentiality.</description><taxo:topics xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/">
      <rdf:Bag xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#">
        <rdf:li rdf:resource="http://delicious.com/ellispratt/documentation" />
        <rdf:li rdf:resource="http://delicious.com/ellispratt/technical-author" />
        <rdf:li rdf:resource="http://delicious.com/ellispratt/technical-communicators" />
      </rdf:Bag>
    </taxo:topics><feedburner:origLink>http://www.cherryleaf.com/blog/2009/03/facilitated-mentoring-meetings-for-documentation-managers/</feedburner:origLink></item><item><title>Manager’s guide to single sourcing: What’s the problem, why is there a need? Cherryleaf Technical Authors Cherryleaf Technical Authors Blog [del.icio.us]</title><link>http://feedproxy.google.com/~r/CherryleafTechnicalAuthorsBlog/~3/WWcBY0gh8ms/</link><category>single-sourcing, documentation, technical-communication , technical-author</category><dc:creator>ellispratt</dc:creator><pubDate>Mon, 30 Mar 2009 06:27:41 PDT</pubDate><guid isPermaLink="false">http://www.cherryleaf.com/blog/2009/03/managers-guide-to-single-sourcing-whats-the-problem-why-is-there-a-need/</guid><description>I thought it might be useful to look at a simple question: Why is there a need for single sourcing technical documentation? For people who aren’t technical authors, it’s often unclear why technical authors talk so much about “single sourcing”. Isn’t that just cutting and pasting? What’s the problem?</description><taxo:topics xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/">
      <rdf:Bag xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#">
        <rdf:li rdf:resource="http://delicious.com/ellispratt/single-sourcing%2C" />
        <rdf:li rdf:resource="http://delicious.com/ellispratt/documentation%2C" />
        <rdf:li rdf:resource="http://delicious.com/ellispratt/technical-communication" />
        <rdf:li rdf:resource="http://delicious.com/ellispratt/%2C" />
        <rdf:li rdf:resource="http://delicious.com/ellispratt/technical-author" />
      </rdf:Bag>
    </taxo:topics><feedburner:origLink>http://www.cherryleaf.com/blog/2009/03/managers-guide-to-single-sourcing-whats-the-problem-why-is-there-a-need/</feedburner:origLink></item><item><title>Cherryleaf Technical Authors' Blog: How barcodes could be the technical author's best new friend [del.icio.us]</title><link>http://feedproxy.google.com/~r/CherryleafTechnicalAuthorsBlog/~3/z2XotHW12Xk/how-barcodes-could-be-technical-authors.html</link><category>information-designer instructional-designer</category><dc:creator>ellispratt</dc:creator><pubDate>Wed, 11 Mar 2009 03:26:02 PDT</pubDate><guid isPermaLink="false">http://www.cherryleaf.com/2009/03/how-barcodes-could-be-technical-authors.html</guid><description>The latest mobile phones in the UK are using barcodes to provide one of the first practical applications of augmented reality. It&amp;#039;s technology that could see barcodes appear on thousands of physical items - something which would open up new opportunities for technical authors providing user assistance for equipment.</description><taxo:topics xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/">
      <rdf:Bag xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#">
        <rdf:li rdf:resource="http://delicious.com/ellispratt/information-designer" />
        <rdf:li rdf:resource="http://delicious.com/ellispratt/instructional-designer" />
      </rdf:Bag>
    </taxo:topics><feedburner:origLink>http://www.cherryleaf.com/2009/03/how-barcodes-could-be-technical-authors.html</feedburner:origLink></item><item><title>Cherryleaf Technical Authors' Blog: Should you appoint a Director of Content? [del.icio.us]</title><link>http://feedproxy.google.com/~r/CherryleafTechnicalAuthorsBlog/~3/F0sHZ30M7oA/should-you-appoint-director-of-content.html</link><category>technical-communicators technical-author documentation, technical-communication</category><dc:creator>ellispratt</dc:creator><pubDate>Wed, 04 Mar 2009 08:39:07 PST</pubDate><guid isPermaLink="false">http://www.cherryleaf.com/2009/02/should-you-appoint-director-of-content.html</guid><taxo:topics xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/">
      <rdf:Bag xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#">
        <rdf:li rdf:resource="http://delicious.com/ellispratt/technical-communicators" />
        <rdf:li rdf:resource="http://delicious.com/ellispratt/technical-author" />
        <rdf:li rdf:resource="http://delicious.com/ellispratt/documentation%2C" />
        <rdf:li rdf:resource="http://delicious.com/ellispratt/technical-communication" />
      </rdf:Bag>
    </taxo:topics><feedburner:origLink>http://www.cherryleaf.com/2009/02/should-you-appoint-director-of-content.html</feedburner:origLink></item><item><title>Cherryleaf Technical Authors' Blog: What can a Technical Author learn from a TV shopping channel? [del.icio.us]</title><link>http://feedproxy.google.com/~r/CherryleafTechnicalAuthorsBlog/~3/0akdvf25uag/what-can-technical-author-learn-from-tv.html</link><category>technical-author, technical-communication</category><dc:creator>ellispratt</dc:creator><pubDate>Wed, 04 Mar 2009 08:37:47 PST</pubDate><guid isPermaLink="false">http://www.cherryleaf.com/2009/02/what-can-technical-author-learn-from-tv.html</guid><description>Different ways in which technical authors can sue the ideas from TV shopping channels in User Assistance.</description><taxo:topics xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/">
      <rdf:Bag xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#">
        <rdf:li rdf:resource="http://delicious.com/ellispratt/technical-author%2C" />
        <rdf:li rdf:resource="http://delicious.com/ellispratt/technical-communication" />
      </rdf:Bag>
    </taxo:topics><feedburner:origLink>http://www.cherryleaf.com/2009/02/what-can-technical-author-learn-from-tv.html</feedburner:origLink></item><item><title>Cherryleaf Technical Authors' Blog: Microsoft Help v.3 Preview [del.icio.us]</title><link>http://feedproxy.google.com/~r/CherryleafTechnicalAuthorsBlog/~3/Umq-svx_kbw/microsoft-help-v3-preview.html</link><category>documentation, Help-3 Help, technical-author user-documentation technical-communication</category><dc:creator>ellispratt</dc:creator><pubDate>Wed, 04 Mar 2009 08:36:11 PST</pubDate><guid isPermaLink="false">http://www.cherryleaf.com/2009/02/microsoft-help-v3-preview.html</guid><description>News and a video about Microsoft&amp;#039;s new technology for online Help</description><taxo:topics xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/">
      <rdf:Bag xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#">
        <rdf:li rdf:resource="http://delicious.com/ellispratt/documentation%2C" />
        <rdf:li rdf:resource="http://delicious.com/ellispratt/Help-3" />
        <rdf:li rdf:resource="http://delicious.com/ellispratt/Help%2C" />
        <rdf:li rdf:resource="http://delicious.com/ellispratt/technical-author" />
        <rdf:li rdf:resource="http://delicious.com/ellispratt/user-documentation" />
        <rdf:li rdf:resource="http://delicious.com/ellispratt/technical-communication" />
      </rdf:Bag>
    </taxo:topics><feedburner:origLink>http://www.cherryleaf.com/2009/02/microsoft-help-v3-preview.html</feedburner:origLink></item><item><title>Cherryleaf Technical Authors' Blog: Twittering Technical Communicators [del.icio.us]</title><link>http://feedproxy.google.com/~r/CherryleafTechnicalAuthorsBlog/~3/i8-JdGBlQ2s/twittering-technical-communicators.html</link><category>technical-author user-documentation documentation, technical-communicators , Twitter, technical-communication</category><dc:creator>ellispratt</dc:creator><pubDate>Wed, 04 Mar 2009 08:34:36 PST</pubDate><guid isPermaLink="false">http://www.cherryleaf.com/2009/02/twittering-technical-communicators.html</guid><description>List of Technical Communicators who Tweet on Twitter.</description><taxo:topics xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/">
      <rdf:Bag xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#">
        <rdf:li rdf:resource="http://delicious.com/ellispratt/technical-author" />
        <rdf:li rdf:resource="http://delicious.com/ellispratt/user-documentation" />
        <rdf:li rdf:resource="http://delicious.com/ellispratt/documentation%2C" />
        <rdf:li rdf:resource="http://delicious.com/ellispratt/technical-communicators" />
        <rdf:li rdf:resource="http://delicious.com/ellispratt/%2C" />
        <rdf:li rdf:resource="http://delicious.com/ellispratt/Twitter%2C" />
        <rdf:li rdf:resource="http://delicious.com/ellispratt/technical-communication" />
      </rdf:Bag>
    </taxo:topics><feedburner:origLink>http://www.cherryleaf.com/2009/02/twittering-technical-communicators.html</feedburner:origLink></item><item><title>Cherryleaf Technical Authors' Blog: Why bother with user documentation in recessionary times? [del.icio.us]</title><link>http://feedproxy.google.com/~r/CherryleafTechnicalAuthorsBlog/~3/_pOU8xFVkdQ/why-bother-with-user-documentation-in.html</link><category>user-documentation , technical-author documentation,</category><dc:creator>ellispratt</dc:creator><pubDate>Wed, 04 Mar 2009 08:33:03 PST</pubDate><guid isPermaLink="false">http://www.cherryleaf.com/2009/02/why-bother-with-user-documentation-in.html</guid><description>Reasons why user documentation is important even in recessionary times.</description><taxo:topics xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/">
      <rdf:Bag xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#">
        <rdf:li rdf:resource="http://delicious.com/ellispratt/user-documentation" />
        <rdf:li rdf:resource="http://delicious.com/ellispratt/%2C" />
        <rdf:li rdf:resource="http://delicious.com/ellispratt/technical-author" />
        <rdf:li rdf:resource="http://delicious.com/ellispratt/documentation%2C" />
      </rdf:Bag>
    </taxo:topics><feedburner:origLink>http://www.cherryleaf.com/2009/02/why-bother-with-user-documentation-in.html</feedburner:origLink></item><item><title>Cherryleaf Technical Authors' Blog: How Pico Projectors could help the Technical Author of the future [del.icio.us]</title><link>http://feedproxy.google.com/~r/CherryleafTechnicalAuthorsBlog/~3/xDpPFfYvK_o/how-pico-projectors-could-help.html</link><category>technical author, technology, pico projectors, documentation</category><dc:creator>ellispratt</dc:creator><pubDate>Wed, 04 Mar 2009 08:31:12 PST</pubDate><guid isPermaLink="false">http://www.cherryleaf.com/2009/02/how-pico-projectors-could-help.html</guid><description>Blog on how Pico projectors could be of particular interest to those writing documentation that&amp;#039;s used in factories, workshops and other areas unsuited to computers and paper manuals.</description><taxo:topics xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/">
      <rdf:Bag xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#">
        <rdf:li rdf:resource="http://delicious.com/ellispratt/technical" />
        <rdf:li rdf:resource="http://delicious.com/ellispratt/author%2C" />
        <rdf:li rdf:resource="http://delicious.com/ellispratt/technology%2C" />
        <rdf:li rdf:resource="http://delicious.com/ellispratt/pico" />
        <rdf:li rdf:resource="http://delicious.com/ellispratt/projectors%2C" />
        <rdf:li rdf:resource="http://delicious.com/ellispratt/documentation" />
      </rdf:Bag>
    </taxo:topics><feedburner:origLink>http://www.cherryleaf.com/2009/02/how-pico-projectors-could-help.html</feedburner:origLink></item><item><title>OnlyWire will immediately boost your website traffic [del.icio.us]</title><link>http://feedproxy.google.com/~r/CherryleafTechnicalAuthorsBlog/~3/RVLEYJYvoiQ/</link><category>onlywire</category><dc:creator>ellispratt</dc:creator><pubDate>Wed, 04 Mar 2009 08:06:48 PST</pubDate><guid isPermaLink="false">http://www.onlywire.com/</guid><description>OnlyWire is the fastest, easiest way to submit web content to all of your social bookmarking sites automatically.

Using a stable, secure and optimized platform for enhanced performance and reliability, OnlyWire is now BETTER, FASTER and FULLY SUPPORTED. OnlyWire users can share and distribute their online content to the range of social bookmarking sites, for increased traffic, increased backlinks and improved search engine index speed.

OnlyWire allows you to manage submissions automatically with The Power of the Button..</description><taxo:topics xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/">
      <rdf:Bag xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#">
        <rdf:li rdf:resource="http://delicious.com/ellispratt/onlywire" />
      </rdf:Bag>
    </taxo:topics><feedburner:origLink>http://www.onlywire.com/</feedburner:origLink></item><item><title>Cherryleaf - Keeping customers through great user documentation [del.icio.us]</title><link>http://feedproxy.google.com/~r/CherryleafTechnicalAuthorsBlog/~3/UB37vmoko9g/</link><category>robohelp help authorit webworks authors communicator writing manual documentation explain cherryleaf armada training trainers</category><dc:creator>ellispratt</dc:creator><pubDate>Thu, 09 Jun 2005 07:55:19 PDT</pubDate><guid isPermaLink="false">http://www.cherryleaf.com/</guid><taxo:topics xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/">
      <rdf:Bag xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#">
        <rdf:li rdf:resource="http://delicious.com/ellispratt/robohelp" />
        <rdf:li rdf:resource="http://delicious.com/ellispratt/help" />
        <rdf:li rdf:resource="http://delicious.com/ellispratt/authorit" />
        <rdf:li rdf:resource="http://delicious.com/ellispratt/webworks" />
        <rdf:li rdf:resource="http://delicious.com/ellispratt/authors" />
        <rdf:li rdf:resource="http://delicious.com/ellispratt/communicator" />
        <rdf:li rdf:resource="http://delicious.com/ellispratt/writing" />
        <rdf:li rdf:resource="http://delicious.com/ellispratt/manual" />
        <rdf:li rdf:resource="http://delicious.com/ellispratt/documentation" />
        <rdf:li rdf:resource="http://delicious.com/ellispratt/explain" />
        <rdf:li rdf:resource="http://delicious.com/ellispratt/cherryleaf" />
        <rdf:li rdf:resource="http://delicious.com/ellispratt/armada" />
        <rdf:li rdf:resource="http://delicious.com/ellispratt/training" />
        <rdf:li rdf:resource="http://delicious.com/ellispratt/trainers" />
      </rdf:Bag>
    </taxo:topics><feedburner:origLink>http://www.cherryleaf.com/</feedburner:origLink></item></channel>
</rss>
