<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
	<title>Presentations&gt;Documentation&gt;Help</title>	<link>http://tc.eserver.org/dir/Presentations/Documentation/Help</link>
	<description>A listing of the most recently indexed works about Presentations and Documentation and Help 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>Presentations&gt;Documentation&gt;Help</title>
		<link>http://tc.eserver.org/dir/Presentations/Documentation/Help</link>
	</image>
	<item>
		<title>A Comparison of Three Visual Help Authoring Tools</title>
		<link>http://tc.eserver.org/35322.html</link>
		<guid>http://tc.eserver.org/35322.html</guid>
		<description>What Are These Tools? Screen recorders that let you: record a series of screens as frames in a movie – like chaining together screen shots; annotate the frames with text captions, high-lights, and other effects for enhanced learning and explanation; add testing – informally through “dead-end” quizzes or formally using eLearning; publish the result.</description>
	</item>
	<item>
		<title>Analyzing Your Deliverables: Developing the Optimal Documentation Library</title>
		<link>http://tc.eserver.org/35338.html</link>
		<guid>http://tc.eserver.org/35338.html</guid>
		<description>Web 2.0 includes: wikis, podcasts, blogs, widgets/gadgets, social networks … and combinations of all the above. Not everyone contributes equally – Creators (18%), Critics (25%), Spectators (48%). But all are important.</description>
	</item>
	<item>
		<title>WinHelp, WebHelp, AIR... Help!</title>
		<link>http://tc.eserver.org/34420.html</link>
		<guid>http://tc.eserver.org/34420.html</guid>
		<description>Online formats can be confusing—consider &quot;WebHelp&quot; vs. &quot;Web Help.&quot; This session describes XML, XHTML, HTML Help, WebHelp, DotNet Help, AIR, and others—and how to select the appropriate one.</description>
	</item>
	<item>
		<title>Think Simple: A Fresh Approach to User Assistance</title>
		<link>http://tc.eserver.org/34063.html</link>
		<guid>http://tc.eserver.org/34063.html</guid>
		<description>Online help. User assistance. That thing that pops up when you press F1. No matter what you call it, user assistance is an important element in the experience of a user. It can mean the difference between a frustrated user and a productive one.&#xD;&#xD;But is today&apos;s user assistance all it can be? Are we giving users purposeful information at the right time, in the most effective format, and ultimately in the way that they need it? Unfortunately, no.</description>
	</item>
	<item>
		<title>Choosing a Help Authoring Tool</title>
		<link>http://tc.eserver.org/31973.html</link>
		<guid>http://tc.eserver.org/31973.html</guid>
		<description>Discusses in detail why you might want to consider a specific tool for help authoring.</description>
	</item>
	<item>
		<title>Creating Help in the Web 2.0 Age</title>
		<link>http://tc.eserver.org/28749.html</link>
		<guid>http://tc.eserver.org/28749.html</guid>
		<description>This is a presentation titled &apos;Creating Help in the Web 2.0 Age&apos; that Neil Perlin gave to the Suncoast Chapter in Tampa, Florida in February 2007. Neil talks about what Web 2.0 is, and how help can be delivered on the fly according to specific user requests.</description>
	</item>
	<item>
		<title>Top Ten Blunders</title>
		<link>http://tc.eserver.org/26204.html</link>
		<guid>http://tc.eserver.org/26204.html</guid>
		<description>Common goofs, mistakes, bloopers, mal mots, slip ups, lapses, oversights, gaffes, and &apos;foe paws&apos; in online documentation and Help.</description>
	</item>
	<item>
		<title>Designing Multi-Platform Online Help: A Demonstration</title>
		<link>http://tc.eserver.org/18225.html</link>
		<guid>http://tc.eserver.org/18225.html</guid>
		<description>Designing multi-platform online help can be&#xD;made more efficient by placing special effort in&#xD;the design of the development plan. If the&#xD;development plan is broken up into four key&#xD;elements the resulting multi-platform design will&#xD;yield a great amount of latitude for both&#xD;maintenance and future enhancements. During&#xD;the demonstration we will discuss our use of&#xD;these elements to design both online and&#xD;hardcopy documentation to support both a&#xD;mainframe and a windows interface.</description>
	</item>
	<item>
		<title>Creating Online Help in a Multiplatform Environment</title>
		<link>http://tc.eserver.org/18219.html</link>
		<guid>http://tc.eserver.org/18219.html</guid>
		<description>With the explosion of online help authoring tools&#xD;(primarily in the Windows® environment)&#xD;companies are clamoring for the ability to produce&#xD;online help on multiple platforms. This&#xD;demonstration presents one solution to the problem&#xD;of creating online help in a multiplatform&#xD;environment. We will demonstrate the process of&#xD;translating FrameMaker™ files from the&#xD;Macintosh® to Windows NT®, and ultimately, to&#xD;UNIX®.</description>
	</item>
	<item>
		<title>Software Reuse, Processes—Essentials for the Trainer’s Toolbox and Single-Source, Multimode Document Delivery</title>
		<link>http://tc.eserver.org/14560.html</link>
		<guid>http://tc.eserver.org/14560.html</guid>
		<description>Traditionally, custom document production begins&#xD;with an empty “New” electronic document and with&#xD;the writer confined to the paper delivery mode. Networked&#xD;software reuse facilities can allow writers to&#xD;avoid this requirement of continually starting from&#xD;scratch. Hence, net worked software reuse may&#xD;provide a framework for efficiently creating custom&#xD;documents in either academic or industrial settings&#xD;for single-source, multimode delivery (Reece, 1993-&#xD;1994). More importantly, software reuse facilities&#xD;may also provide common ground for technical&#xD;training within a variety of computing environments.&#xD;This paper defines software reuse, recommends&#xD;a process for the development of documents&#xD;in a software reuse facility, and provides information&#xD;on quality characteristics for evaluating such&#xD;software.</description>
	</item>
	<item>
		<title>Low-End Online Documentation Viewing Systems: Why and How</title>
		<link>http://tc.eserver.org/14550.html</link>
		<guid>http://tc.eserver.org/14550.html</guid>
		<description>Online documentation is now widely accepted for&#xD;its convenience and cost savings. However, some&#xD;small, non-Windows shops find very few offerings&#xD;in the market place for online documentation&#xD;software.</description>
	</item>
	<item>
		<title>A “Real World” Look at Windows Help Authoring Tools</title>
		<link>http://tc.eserver.org/14548.html</link>
		<guid>http://tc.eserver.org/14548.html</guid>
		<description>Aha, you say, you’ve finally gotten permission to go online.&#xD;And your boss has even allocated enough precious-budget&#xD;dollars to buy the right hardware and software to do the job.&#xD;How hard can if be to find a good authoring tool, you think.&#xD;And then you start to receive the product literature from n&#xD;developers of Windows help authoring tools . . .&#xD;</description>
	</item>
	<item>
		<title>Using Word to Create Windows Help</title>
		<link>http://tc.eserver.org/14551.html</link>
		<guid>http://tc.eserver.org/14551.html</guid>
		<description>One way to create Windows help is by using Word for&#xD;Windows. To begin, you must become familiar with the&#xD;help concepts of topics and hyperlinks. Then, you create&#xD;these components: projectile, header file, and source&#xD;files. Source files are created using Word for Windows.&#xD;Next create the actual help file by compiling the elements&#xD;you have created. Finally, view and debug the results.</description>
	</item>
	<item>
		<title>Designing an Online Help System Before the Interface is Ready</title>
		<link>http://tc.eserver.org/14366.html</link>
		<guid>http://tc.eserver.org/14366.html</guid>
		<description>Developing a Windows online help system that clients can use effectively and bringing it in on time and within budget is a challenging task. You can dramatically improve your chances of success by doing the following: Develop help as sofnvae is being developed (and even before!); Chunk information for easy reading and to facilitate&#xD;reuse by other writers; Create design and style guidelines to cut down peer review and editing time; Develop and use information webs to cut down on technical review time; Integrate the information web and the user interface to&#xD;complete your help system.</description>
	</item>
	<item>
		<title>Is Online “lnline” with Your Users’ Needs?</title>
		<link>http://tc.eserver.org/14372.html</link>
		<guid>http://tc.eserver.org/14372.html</guid>
		<description>In preparation for the next release of our flagship&#xD;so~are product, the International Publications&#xD;Department at Waters Corporation wanted to assess&#xD;the usefulness of our current product software&#xD;documentation with the idea of moving the next&#xD;generation of documentation in the direction&#xD;requested by our customers. Based on extensive customer contact, we formulated a plan to dramatically revamp the documentation, namely to&#xD;replace the paper user’s guides and transform our&#xD;existing online Help into a comprehensive Online&#xD;User’s Guide.</description>
	</item>
	<item>
		<title>The Key for Effective Documentation: Answer the User’&apos;s Real Question</title>
		<link>http://tc.eserver.org/14351.html</link>
		<guid>http://tc.eserver.org/14351.html</guid>
		<description>To successfully communicate to users, documentation must do more than meet the user’s information needs, it must present the information in the same way the user processes the information. The design of sofhYare and&#xD;its accompanying documentation must be reconceived&#xD;so that the design is done porn the problem-solver’s&#xD;pornt of view. Effectively designing documentation&#xD;requires the writer to: start with the user, answer the&#xD;user’s rest questions, optimize all documentation as a&#xD;smgle umt, allowfor user mistakes, and consider how&#xD;you present the information.</description>
	</item>
	<item>
		<title>Where is the Instruction in Online Help? Designing it Right the First Time</title>
		<link>http://tc.eserver.org/14352.html</link>
		<guid>http://tc.eserver.org/14352.html</guid>
		<description>One of the ironic things about online help systems is that they are very often not helpful and even increase the user&apos;s frustration and stress level. A consequence of this&#xD;increased frustration sometimes results in the rejection of&#xD;the software. One solution is to increase the effectiveness&#xD;of online help systems by designing them from an&#xD;instructional design perspective. Some of the things we&#xD;can provide users include: imperative, task-focused&#xD;procedures; graphic feedback; access to redundant&#xD;instructions; links to tutorial practice; philosophical and&#xD;conceptual explanations for “why” they are completing&#xD;specific tasks.</description>
	</item>
	<item>
		<title>Designing a Supplementary Web-Based Online Help System: A Case Study</title>
		<link>http://tc.eserver.org/13301.html</link>
		<guid>http://tc.eserver.org/13301.html</guid>
		<description>Computerized Medical Systems, Inc. (CMS) has&#xD;implemented an extensive online help system based on&#xD;HTML for its FOCUS radiation therapy planning system.&#xD;Netscape Navigator was selected as the browser because&#xD;FOCUS is based on the UNIX platform and Netscape&#xD;was the only HTML browser available for UNIX.&#xD;</description>
	</item>
	<item>
		<title>An Overview of HTML-based Help</title>
		<link>http://tc.eserver.org/13202.html</link>
		<guid>http://tc.eserver.org/13202.html</guid>
		<description>HTML...HTML Help...HTML-based help...WebHelp... JavaHelp...Oracle Help...what does it all mean? There are so many online help options, it’s easy to get overwhelmed and confused. This paper discusses the difference between HTML Help, WebHelp, JavaHelp, and Oracle Help. Specifically, it explains each help technology’s features and limitations, the user requirements, and best use.</description>
	</item>
	<atom:link href="http://tc.eserver.org/dir/Presentations/Documentation/Help.xml" rel="self" type="application/rss+xml"/>
</channel>
</rss>