Customer Support on the Web

Customers avoid web-based customer support if information is not relevant, out of date or hard to find. Without a business commitment to addressing these issues, customers will continue to prefer contacting a service representative by phone.

Szuc, Daniel and Gerry Gaffney. Apogee (2005). Articles>Documentation>Help>Online

Customized Book-Based Electronic Collections: Case Study and Exploration of Issues  

Collections of technical documentation vary in their delivery media, file format, user interface and degree of integration of the component documents or information. This paper looks at definitions and attributes of collections before reviewing the development of book- based, customized CD collections in a company operating in a fast-changing industry. Issues arising from this case study are explored and findings are used to identify a broad categorization of collections and build a starting point check list for collection design. Major issues in collection building are summarized.

Symonds, Yosef. STC Proceedings (2004). Articles>Documentation>Online>Case Studies

The Death of Paper Manuals

I'll pay $20 for a manual. I'd even pay $30-40 for a manual (grudgingly...). But $65 for a manual that should be in the damn box to begin with? Sorry... NO.

DealMac (2003). Articles>Documentation>Online>Help

Delivering Documentation on CD-ROM and the Internet  

Many companies produce products on the cutting edge of technology but still publish documentation using old technology. At N.E.T., we develop our information with the goal of using the latest technologies; this includes using the Internet and CDROM as our primary modes of delivery.

Jones, Margaret and Pat Adams. STC Proceedings (1998). Articles>Documentation>Online

Delivering Training and Support Using Windows Help  

The Windows Help utility is familiar as a tool to provide context-sensitive and procedural help for people using a software application, but it also a highly effective tool for providing many kinds of desktop-based training and support within an organization. During this session, we look at a variety of systems built using Windows Help and explore why this was a good choice for the particular project.

Deaton, Mary M. STC Proceedings (1997). Articles>Documentation>Online>Help

Design Checklists for Online Help

Online help systems have evolved over the past 20 years to meet the needs of our users. Designers must consider the content, format, presentation, navigation, and access methods of online help systems. A series of design checklists based on the past 20 years of research are presented in this paper, which summarizes a journal article currently being considered for publication. The latest trend in online help system design is embedded user assistance, which includes integrating information into the interface and including an embedded help pane within that interface to display a context-sensitive online help system.

Corbin Nichols, Michelle. WritersUA (2004). Articles>Documentation>Help>Online

Designing a Product Documentation Library for the World Wide Web  

Designing a documentation library for the WWW requires understanding the unique capabilities of the Web and how they can be used to meet the documentation needs of customers. The Web is ideal for distributing information and interacting with customers, but certain considerations apply. Will you offer free Web access to manuals you normally sell? If you choose to limit library access to customers, how will you prevent unauthorized browsing? Do you want to use the Web to solicit readers’ comments? With the Web, you can effortlessly distribute new versions of documentation, but you must carefully identify each version to avoid customer support problems.

Bassow, Fern and Holly Gross. STC Proceedings (1996). Articles>Documentation>Online

Designing a Software User Assistance System

This article looks at a methodology for developing a software user assistance (UA) system in a structured manner. The software UA system could have both paper-based user manuals and online help systems.

Ferris, Tamara. Indus (2006). Articles>Documentation>Online>Help

Designing Information for the Online Medium  

Well-designed online documentation exploits the medium to make the content more accessible and effective. Knowing who needs the information and understanding when and how much of it will be used are essential for the creation of effective online content. Ideally, online documentation should answer each question with just the right amount of depth and detail. Considering user expertise, information needs, and usage patterns before creating the content or structure results in information that can be scanned, searched, surfed, referred to, read, or printed equally effectively—exactly what people expect from online documentation.

Mehrotra, Rahul and Jane Nye. STC Proceedings (1998). Articles>Documentation>Online

Developing HTML Documents and Help System  

This document explains necessary tips for providing product information in digital form, giving specific examples of choosing the suitable media, classifying information, appropriate linking, file organization, etc. through our experience (in Fuji Xerox Co., Ltd.) during the development of the software product called Web PrintVision.

Ito, Sachi. STC Proceedings (1998). Articles>Documentation>Online>Help

Developing Online Help for OS/2 Applications  

One of the biggest problems facing Help developers is that of providing users with adequate methods of navigation through what can be huge amounts of information. After more than a two or three jumps, users can find themselves in topics that might be useful, but with no clear indication of how they got there or how to return to where they started. OS/2 gives the Help developer extraordinarily flexible tools for creating online documentation that can prevent this situation and provide users with a clearer path through online information than many other platforms can provide. However, this enhanced usability is not without its cost.

Radecki, Steven Lewis. STC Proceedings (1993). Articles>Documentation>Online>Help

Developing Online Help in Lotus Notes  

If you are a technical writer or manage technical writers and have been asked to document Lotus Notes applications, this workshop will give you a jump start. You can use the features available in Notes to create an effective help system as a Notes database. This help database can either be a view in an existing Notes application or a stand-alone database linked to the application. In this workshop, you will learn the basics of creating help systems in Lotus Notes.

Gross, Jacqui, Faye Smith and Steve Charles. STC Proceedings (1998). Articles>Documentation>Help>Online

Developing WebHelp: What 'How to' Design Doesn't Always Tell Us  

Development of the Intranet application STAR.IDN for requesting and receiving medically related supplies illustrates a broad spectrum of technological and user issues. As such it serves as a case study of design and user-related decisions between an application designer and a Help author. Central to the study is the argument that design must be based on an empirically 'informed' rather than 'assumed' user model. The project also challenges Web literature that does not address user considerations in its promotion of design methods.

Eiler, Mary Ann and Kathleen Bright. STC Proceedings (1998). Articles>Documentation>Online>Help

Distributing Cross-Platform, Cross-Browser HTML Help Using the Microsoft Java Applet  

In a previous article we discussed what browser-based HTML Help is, and how you can use the HTML Help ActiveX control to create and distribute web-based HTML Help to Microsoft Internet Explorer Users. In this article we'll explain how to use the Microsoft Java Applet to create and distribute Help systems that can be viewed by an Java-enabled browser.

ComponentOne (1999). Articles>Documentation>Online>Help

Distributing Web-based HTML Help

In this article we discuss what browser-based HTML Help is, the sitemap file that's behind the HTML Help table of contents, how the HTML Help ActiveX control HHCTRL.OCX interprets and displays this sitemap file, and how you can automatically distribute HHCTRL.OCX.

ComponentOne (1998). Articles>Documentation>Online>Help

The Documentation Elephant

As technical writers, we work more online than ever before. We are beginning to work with documentation in a new way, so that we can repurpose content and free it from the restrictions imposed by any particular delivery mechanism. We no longer solely create paper-publishable documents. We do not, as yet, have a good word for what we do; we do not have a single word or phrase that summarizes the effort or the deliverables. Nor can we use any single existing lexicon because the concepts are new. This difficulty is a natural consequence of the inter-networked world in which we work, where information is delivered multiple ways for diverse audiences. But let us look at the phrases currently growing in popular usage that refer to this effort.

Albing, Bill, Michelle Corbin Nichols and Ann-Marie Grissino. Carolina Communique (2004). Articles>Documentation>Online

Documentation on CD-ROM: Strategies for a Successful Implementation  

Producing documentation on CD-ROM can be extremely beneficial to users and can also save your company a lot of money over hard copy costs. To assure a successful roll-out of your CD product, it is critical to consider the involvement of key departments in your company as you plan the implementation in your user community. The two processes are closely related, and a well-integrated internal plan will help assure a successful introduction to your customers.

Florsheim, Stewart J. STC Proceedings (1994). Articles>Documentation>Online

Documenting in N Dimensions

It is commonplace to find information through the Web, but the use of the Web for technical communication is still uncommon. What the competition entries made me realize is that in this networked world, the places where we find information are no longer one or two dimensional. Communication is no longer simply about words on a page (or on a screen). Technical information is now accessed through a multidimensional cyberspace.

Albing, Bill. Carolina Communique (2004). Articles>Documentation>Online

A Dozen Techniques to Improve Your Software Online Help

There are several main reasons why putting your software manual on-line is necessary. It makes your web-site attractive for search engine crawlers and therefore brings you targeted traffic from Google, Yahoo!, MSN, and other search engines. A good online manual presents your product as serious and credible. Moreover, if a user faces difficulty using your software and asks for technical support, you may easily resolve the issue by referring that user to a certain page of your online help. Simply give the page's URL. With just one click the user will see screenshots and explanations which will help them to resolve the issue.

Crane, Dennis. Dr. Explain (2005). Articles>Documentation>Online>Help

Electronic Document Production  

This encyclopedia article provides engineering managers with a detailed overview of the process for developing online documents.

Hayhoe, George F. George Hayhoe Associates. Articles>Documentation>Online

Electronic Documentation Basics

Below you can find a compilation of the most frequently asked questions about electronic catalogs. You will find answers to general as well as to technical questions.

ITEDO Software (2003). Articles>Documentation>Online>Help

Electronic Information Kiosks: A New Online Genre for Technical Communicators  

Kiosk design is an inevitable extension of the development of online documentation. Technical communicators are now frequently being asked by their employers to create such forms of communication. They must learn about kiosks from the new perspectives of their evolving technologies, applications, audience reactions, social contexts, and information design. Finally, technical communicators must begin to view kiosks as an emerging new genre that requires both analysis and creativity.

Shirk, Henrietta Nickels. STC Proceedings (1996). Articles>Documentation>Online

Embedded Help – Meeting the Needs of Your Users  

Designing and developing an embedded help solution involves several stages. A successful solution starts with identifying user wants and needs. As you sort through these needs, identify common threads and design a solution that addresses these common threads. Consistency, flexibility, and experimentation are keys to developing a successful solution. Your design should be intuitive to use, and should provide users with the options they need. As you design your solution, consider your develop and maintenance requirements. You want the time you invest in the first version of your solution to pay off for future releases.

Mueller, Paul. STC Proceedings (1999). Articles>Documentation>Online>Help

The Evolution of a Help System  

An industry-wide design standard for help systems does not exist. To develop a flexible and usable help system for our workstation-based product, we have evolved and changed our help system design. Over a five-year period our help system was influenced by several factors:

Caldanaro, Regina M. and Michelle Corbin Nichols. STC Proceedings (1995). Articles>Documentation>Online>Help