<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
	<title>Reference&gt;Writing&gt;Technical Writing</title>	<link>http://tc.eserver.org/dir/Reference/Writing/Technical-Writing</link>
	<description>A listing of the most recently indexed works about Reference and Writing and Technical Writing in the field of technical communication (and technical writing).</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>Reference&gt;Writing&gt;Technical Writing</title>
		<link>http://tc.eserver.org/dir/Reference/Writing/Technical-Writing</link>
	</image>
	<item>
		<title>Quick Reference Guides Are More Useful Than a 150-Page User Doc</title>
		<link>http://tc.eserver.org/35804.html</link>
		<guid>http://tc.eserver.org/35804.html</guid>
		<description>I’m working on a project to boil a 150-page software user document down to a one-page reference guide that can be tacked to a CSR’s cube wall. Our goal with the one-page reference guide is to give the CSR a description of all the navigation elements and application functionality so they can quickly navigate to where they want to go without first having to trudge through the complete 150-page user doc.</description>
	</item>
	<item>
		<title>Quick Reference Guides: Short and Sweet Technical Documentation</title>
		<link>http://tc.eserver.org/34382.html</link>
		<guid>http://tc.eserver.org/34382.html</guid>
		<description>Users often want documentation in a format that will give &#xD;them the basics and get them on their way as fast as &#xD;possible. Quick reference guides provide a short version of &#xD;a manual, condensed from dozens or hundreds of pages &#xD;down to just one double-sided sheet of paper. Despite the &#xD;brevity of quick reference material, the thought process &#xD;involved in creating, organizing, and laying out the &#xD;content is time consuming. The format requires you to &#xD;assess the content and decide the most important &#xD;information the user needs to know. You must describe &#xD;with extreme concision and clarity processes that usually &#xD;require dozens of pages to explain. &#xD;This article provides an overview of the strategies, tips, &#xD;challenges, and benefits we have learned in using quick &#xD;reference guides for our documentation projects.</description>
	</item>
	<item>
		<title>Quick Reference Guides: Short and Sweet Documentation</title>
		<link>http://tc.eserver.org/34252.html</link>
		<guid>http://tc.eserver.org/34252.html</guid>
		<description>In this article, my colleague and I provide strategies, tips, and approaches we’ve learned in creating quick reference guides for software documentation projects.</description>
	</item>
	<item>
		<title>Technical Writing Guide</title>
		<link>http://tc.eserver.org/34159.html</link>
		<guid>http://tc.eserver.org/34159.html</guid>
		<description>This set of guidelines was developed to help you understand the expectations for technical communication in CE 314K (Properties and Behavior of Engineering Materials). Successful technical communication requires practice. Therefore, you should allot sufficient time to write several drafts of each assignment before submitting the final version.</description>
	</item>
	<item>
		<title>Comunicazione Tecnica</title>
		<link>http://tc.eserver.org/26969.html</link>
		<guid>http://tc.eserver.org/26969.html</guid>
		<description>Il processo di comunicazione tecnica consiste nel veicolare informazioni circa una tecnologia ad una platea ben definita.</description>
	</item>
	<item>
		<title>Technical Writer</title>
		<link>http://tc.eserver.org/24963.html</link>
		<guid>http://tc.eserver.org/24963.html</guid>
		<description>A hypertext encyclopedia entry about technical writers, with links to many related topics.</description>
	</item>
	<item>
		<title>Technical Report Overview</title>
		<link>http://tc.eserver.org/24117.html</link>
		<guid>http://tc.eserver.org/24117.html</guid>
		<description>This outline is provided to help introduce the Technical Report and to clarify the acceptable format and level of achievement that is considered essential for successful completion of the Technical Report.</description>
	</item>
	<item>
		<title>Engineering Communication Centre</title>
		<link>http://tc.eserver.org/23503.html</link>
		<guid>http://tc.eserver.org/23503.html</guid>
		<description>Language Across the Curriculum in Applied Science and Engineering at the University of Toronto helps students to communicate in writing and orally.</description>
	</item>
	<item>
		<title>Guidelines for Technical Writing</title>
		<link>http://tc.eserver.org/23502.html</link>
		<guid>http://tc.eserver.org/23502.html</guid>
		<description>The rules here apply to all classes in the Chemical Engineering Department at Ohio University. Most of them will apply in &apos;the real world&apos;, too, although your employer may have some specific format requirements.</description>
	</item>
	<item>
		<title>Style Manuals and Guides for Technical Writing</title>
		<link>http://tc.eserver.org/20712.html</link>
		<guid>http://tc.eserver.org/20712.html</guid>
		<description>Style manuals show how to format bibliographies and footnotes; some also provide information on outlining, editing and writing. If your instructor has not specified a particular format or recommended a style manual, consult one of the following, widely-used manuals.</description>
	</item>
	<item>
		<title>Apple Publications Style Guide (2003)</title>
		<link>http://tc.eserver.org/19711.html</link>
		<guid>http://tc.eserver.org/19711.html</guid>
		<description>The May 2003 edition of the standard reference for Apple publications.</description>
	</item>
	<item>
		<title>Apple Publications Style Guide (2003)</title>
		<link>http://tc.eserver.org/13518.html</link>
		<guid>http://tc.eserver.org/13518.html</guid>
		<description>An updated version of the style guide used by writers and editors in Apple publications groups.</description>
	</item>
	<item>
		<title>MS HELP 2.0</title>
		<link>http://tc.eserver.org/10681.html</link>
		<guid>http://tc.eserver.org/10681.html</guid>
		<description>MS Help 2.x was announced at WinWriters on March 5, 2001. MS Help 2 is the help system used by Visual Studio .NET help and MSDN Library, and now the Borland .NET IDEs. Getting started with MS Help 2.0? This site is a start.</description>
	</item>
	<atom:link href="http://tc.eserver.org/dir/Reference/Writing/Technical-Writing.xml" rel="self" type="application/rss+xml"/>
</channel>
</rss>