<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
	<title>Porter, Alan J.</title>	<link>http://tc.eserver.org/authors/Porter,_Alan_J.</link>
	<description>A bibliography of works by Porter, Alan J. in the field of technical communication.</description>
	<language>en-us</language>
	<copyright>Copyright (c) 2005-08 by the EServer. All rights reserved.</copyright>
	<managingEditor>tclib-editorial@eserver.org (TC Library Editorial Board)</managingEditor>
	<webMaster>webmaster@eserver.org (Geoffrey Sauer)</webMaster>
	<image>
		<url>http://tc.eserver.org/images/newlogo.gif</url>
		<title>Porter, Alan J.</title>
		<link>http://tc.eserver.org/dir/Porter,_Alan_J.</link>
	</image>
	<item>
		<title>Wikis in the Workplace: a Practical Introduction</title>
		<link>http://tc.eserver.org/35752.html</link>
		<guid>http://tc.eserver.org/35752.html</guid>
		<description>The wiki crops up in many companies&apos; internal discussions about process improvements and efficient collaboration, but it is often shot down because so few people have exposure to good models of what a really successful business wiki can do. Ars is here to help with a practical introduction based on real-world examples.</description>
	</item>
	<item>
		<title>Ten Commandments of Storytelling as Applied to Technical Documentation?</title>
		<link>http://tc.eserver.org/34015.html</link>
		<guid>http://tc.eserver.org/34015.html</guid>
		<description>Anyone who reads this blog will know that I’m a strong advocate of storytelling in all forms of communications. I believe that it applies as much to technical or marketing communication as it does to your favorite novel or movie. This article applies McKee’s 10 Commandments to Technical Documentation.</description>
	</item>
	<item>
		<title>Why Use A Wiki?</title>
		<link>http://tc.eserver.org/33884.html</link>
		<guid>http://tc.eserver.org/33884.html</guid>
		<description>The aim of this paper is to introduce the concept of the Web-based collaborative authoring environment commonly referred to as wikis, and examine how they can be used in a corporate publishing environment. The paper also includes suggested techniques for transferring existing content from native authoring tools into a wiki format for online delivery.</description>
	</item>
	<item>
		<title>The Google Chrome Comic: Why it Didn&apos;t Work</title>
		<link>http://tc.eserver.org/32172.html</link>
		<guid>http://tc.eserver.org/32172.html</guid>
		<description>I&apos;m amazed with the Google project, because the lack of narrative seems like a basic omission from such a high profile project.</description>
	</item>
	<item>
		<title>Why Technical Publishing Shouldn&apos;t Be Art</title>
		<link>http://tc.eserver.org/32174.html</link>
		<guid>http://tc.eserver.org/32174.html</guid>
		<description>The work may start with the author, but to get it from the author to the end reader means it also has to go through an editor, copy editor, book designer, typesetter, printer, sales and marketing team, distributor, book buyer, and, eventually, a retail store.</description>
	</item>
	<item>
		<title>Eliminating the &apos;End Game&apos; from Electronic Deliverables</title>
		<link>http://tc.eserver.org/32189.html</link>
		<guid>http://tc.eserver.org/32189.html</guid>
		<description>Once you start looking at your publishing process separately from your content and style considerations, you will have identified how your “End Game” impacts your production process. Then, you can take the necessary steps to eliminate it.</description>
	</item>
	<item>
		<title>Eliminating the END GAME from Electronic Deliverables</title>
		<link>http://tc.eserver.org/31707.html</link>
		<guid>http://tc.eserver.org/31707.html</guid>
		<description>While executive management may sometimes believe that anyone can write and that a technical writer&apos;s job is to &quot;Just Publish It&quot;, it may be time for technical writers to look at what they can do to improve the &quot;end game&quot; process, which Porter describes as &quot;All the steps needed to create the desired output format – HTML, PDF, online help system, etc. – from the source content.&quot; By taking a closer look at the publishing process, without regard to content, technical communicators may discover ways they can streamline the steps it takes to get content published and ready for the end consumer.</description>
	</item>
	<item>
		<title>Leading Your Company into the Wikis, Blogs, and Social Networks of Web 2.0</title>
		<link>http://tc.eserver.org/31490.html</link>
		<guid>http://tc.eserver.org/31490.html</guid>
		<description>In this podcast, I talk with Alan Porter, vice president of Operations at WebWorks, about the Web 2.0 technologies they’re using to reach out to their customer base. In addition to using blogs, wikis, and social networks to connect with customers, WebWorks also uses wikis to facilitate communication and collaboration within their company.</description>
	</item>
	<atom:link href="http://tc.eserver.org/authors/Porter,_Alan_J..xml" rel="self" type="application/rss+xml"/>
</channel>
</rss>