A directory of resources inthe field of technical communication.

Articles>Documentation>Online>Help

26-49 of 97 found. Page 2 of 4.

About this Site | Advanced Search | Localization | Site Maps
 

« PREVIOUS PAGE 1 2 3 4  NEXT PAGE »

 

26.
#24798

The Evolution of a Help System   (PDF)

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

27.
#21473

Fault Tolerance: A More Forgiving Doc-To-Help and Word for Windows   (PDF)

Doc-To-Help 2000 has a new 'fault tolerance' feature that forgives novice authors their Microsoft Word mistakes, including direct formatting and stretched bookmarks. These problems often cause corrupted cross-references as well as document-to-Help-system conversion problems. Doc-To-Help's automatic diagnostic and repair utilities now find these common errors and correct them automatically.

Wade, Jenny. ComponentOne (1999). Articles>Documentation>Online>Help

28.
#20341

From Information to User Assistance: A Support System for a User Technology Organization   (PDF)

Our plight as users of process information is much like that of the users of the information for our software products. Like them, we want to do useful work and get appropriate assistance when we need it. Instead of just reading about a task such as writing an information plan, we want the templates and samples to use when writing the plan. Just-in-time assistance, experience captured in a useful form, would suit us just fine. This paper, by the designers and developers of a system that supports the work and processes of a user technology organization, presents the information design issues that we encountered and the design of the system that we created.

Hargis, Gretchen, Deirdre Longo and Lindsay Bennion. STC Proceedings (1999). Articles>Documentation>Online>Help

29.
#23661

From Online Help to Embedded User Assistance   (PDF)

Online help systems have evolved over the past twenty 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. STC Proceedings (2003). Articles>Documentation>Online>Help

30.
#19950

Help Is Dead. Long Live Help!   (PDF)

As Help Authors, we often treat online help as a 'thing,' not an activity. We’ve favored the noun over the verb! This preference is natural for writers, who enjoy producing books. If we hope to survive on a dynamic development team, we must train ourselves away from writing books, toward helping people. This shift means examining the bigger picture and adopting different ways of working.

Sisler, Paul and Catherine M. Titta. STC Proceedings (2001). Articles>Documentation>Help>Online

31.
#29926

The Help Landscape: A Mile Wide and 30 Seconds Deep

Two questions any writer must deal with are: 'What do I write about?' and 'How much do I say about it?' Essentially, these questions deal with the scope and the depth of a document. Technical communicators have a tendency to want to document a topic as completely as possible, and we carry this instinct with us when we architect and write Help files. In this column, I challenge that prevalent instinct and offer an alternative way of thinking about the scope and depth requirements of Help systems. The benefits of this approach are, I hope, better Help for users and, for our clients and employers, a more efficient use of technical communicators' time. First, I'll discuss three principles that underpin my perspective, then I'll give some practical advice about writing Help that people will actually use.

Hughes, Michael A. UXmatters (2007). Articles>Documentation>Help>Online

32.
#20161

Help! Six Fixes to Improve the Usability of Your Online Help   (PDF)

Tight deadlines and limited resources often force wiiters to cut corners and release less than optimal help system designs. After considerable trial and error, I te come up with a checklist that can help you evaluate and improve your help system for the next release. Each question represents an important usability issue.

Timpone, Donna. STC Proceedings (1997). Articles>Documentation>Online>Help

33.
#30499

Hero Stuff: Saving 50% on Support Costs with Fax and Modem Support Documents   (PDF)

In the PC products market, customers insist on excellent support at rock-bottom prices. The traditional model of customer support, having a phone technician answer customer questions, is becoming too expensive.

Brown, Constance C. STC Proceedings (1993). Articles>Documentation>Online>Help

34.
#24410

HTML-Based Help: A Convergence of Two Solutions   (PDF)

IDX Systems launched two separate HTML-based help authoring efforts simultaneously. The results were two very different HTML-based help solutions. One solution emphasized thorough and complete information while compromising accessibility. The other solution emphasized accessibility while compromising thoroughness and completeness. In both cases, the compromises were forced by the limitations of current web technologies. The two writing efforts have now been merged into one solution that uses HTML, database technology, and Active Server Pages.

Johnson, Wayne and Fritz Garrison. STC Proceedings (1998). Articles>Documentation>Online>Help

35.
#24407

Implementing Help Systems for Java Applications   (PDF)

Technical communicators are facing a revolution in how we develop online help for software applications. No where is this more apparent than in the development of help systems for applications written in Java. Sun Microsystems, Inc., expects to roll out JavaHelp in the early part of 1998. Until JavaHelp arrives, technical communicators will have to find creative ways to implement HTML help systems for Java applications. The best news is that we have some standards to follow, like HTML, and some methods for browsing HTML help today. The key is to develop scalable help systems designed with the future in mind. This paper discusses some ways you can create HTML help content that works with your applications today and tomorrow.

Colvin, Richard D. STC Proceedings (1998). Articles>Documentation>Online>Help

36.
#25870

Indexing Online Help   (PDF)

In order to make a help system really helpful, you need to provide an effective index. But many online help writers face two dilemmas when it's time to index their help systems: How to prepare a useful index that meets the users' needs and how to code the keywords to make the index compile correctly. This article provides tips to help writers solve both problems.

Hamilton, Beth. STC Indexing SIG (1999). Articles>Documentation>Online>Help

37.
#29988

Indicating Changed Text in Help Files

There are still many circumstances when drawing a user's attention to changed text is important. How do we do that with Help systems? By borrowing techniques from paper manuals, we don't have to reinvent the wheel. So here's a good approach that will work for Microsoft Word-based HATs.

Self, Tony. HyperWrite (2004). Articles>Documentation>Online>Help

38.
#30573

Issues in Designing, Implementing, and Evaluating a Help System   (PDF)

The design team for a major new product approached our publications group about ideas on developing an online manual and/or online help. Together, we developed a task-oriented, easy-to-use online help system, and continue to work together to evaluate it. Where do we best put the buttons that access the help for various subsystems?

Evans, Jeanette P. STC Proceedings (1993). Articles>Documentation>Online>Help

39.
#24212

Key Roles In Developing Successful Online Help   (PDF)

There are many roles involved in developing a successful online help project. Understanding the relationship between these roles can increase everyone's awareness of the requirements and tasks necessary for a successful project. In many projects, individuals fill more than one role, moving between roles as needed.

Hall, Rebecca C. STC Proceedings (1999). Articles>Documentation>Online>Help

40.
#23733

Making Online Help Helpful -- Perspectives of Professionals and Users   (PDF)

This paper reviews research done in online help information, analyses different views on it from the perspectives of professionals of technical communication and end-users, and suggests ways to solve problems.

Li, Yue. STC Proceedings (2003). Articles>Documentation>Online>Help

41.
#24766

Mastering the Mayhem: How to Manage a Hypertext Help Project   (PDF)

Two main forces affect a Help project: absurd deadlines and a complex web of hypertext files. Those responsible for managing such projects often ask: How do I gain control of all these forces? When do I need to start the project? How do I gauge its progress? Our demonstration will show how to successfully manage a Help project. We will illustrate how WordPerfect Domestic Documentation Services solves management problems using a timeline, checklist, and tracking database.

Calhoun, Deirdre and Wendy Fritzke. STC Proceedings (1994). Articles>Documentation>Online>Help

42.
#22860

Maximizing Windows Help   (PDF)

Maximizing Windows Help is more than just converting printed documentation to Help. Help users want easy access to information so that they can complete their tasks expeditiously. A Help topic should contain information that adresses one subject, has one objective, and answers one question. To maximize Windows Help, chunk information and use hyperlinks. The use of macros can enhance how information is accessed.

Smart-Wycislo, Nicole Y. and Patryce Moshay. STC Proceedings (1997). Articles>Documentation>Online>Help

43.
#20118

Migrating to WinHelp 4.0 for Windows ’95   (PDF)

WinHelp 4 is the help environment for Microsoft’s Windows 95 and Windows NT operating systems. Among the important new features of WinHelp 4 are more capable secondary windows, shortcut buttons, the ability to integrate multiple help files, What’s This? help, and better support for online coaches. Help authors must understand both the construction and the design aspects of these new features. They must also deal with the complexities of the transition from Windows 3.1 help to WinHelp 4.

Farkas, David K. and Joe Welinske. STC Proceedings (1996). Articles>Documentation>Online>Help

44.
#24841

A Modular Approach to WinHelp Projects: The Process Behind the Success   (PDF)

The Knowledge Products group at Cisco Systems, Inc., provides online help for both PC and UNIX-based applications. The online help team for the Cisco Works for Windows product comprised of five writers who coordinated the online help development efforts. The online help team worked closely to produce an integrated help system that was modularized for better process control.

Mandavilli, Lavanya K. STC Proceedings (1996). Articles>Documentation>Online>Help

45.
#24805

Moving Beyond Help   (PDF)

Users complain that there is too much information in help. We will explore ways to move beyond help and provide users with the types of support they really need: re-using information on commercial information services such as CompuServe or America Online, on the Internet, and on dial-up phone and fax services. Making application interfaces self-documenting. Providing information in overlaid notes, cue cards, and wizards.

Hyman, Francine N. and Jonathan R. Price. STC Proceedings (1995). Articles>Documentation>Online>Help

46.
#23739

Moving from Paper to Electronic Documentation: Tips for a Successful Project   (PDF)

With new tools and technologies available, more companies are choosing to move from paper-based documentation to electronic documentation. Being a pioneer is an exciting – and daunting – experience. In moving from paper-based to electronic documentation, you may be treading on a path never before explored for your product or your company. There are many decisions to make and many plans to develop, abandon, and develop again. Special attention is required in the areas of project management, writing and illustration, documentation design, and configuration management. A team that has experienced a paper-to-electronic documentation project can offer valuable advice if you are facing a groundbreaking project.

Finan, Jill Sutton, Joanna Natoli, Heather Healy and Mike Kocik. STC Proceedings (2003). Articles>Documentation>Online>Help

47.
#24658

Next Generation Microsoft Online Help

Just as clothing styles change, and fall's fashion is different from summer's, so Microsoft presents it's new fall's fashion of online help to a fashion-consious entourage of software companies always eager to follow Microsoft's lead.

Albing, Bill. KeyContent.org (2004). Articles>Documentation>Online>Help

48.
#29867

Non-Fatal Errors: Creating Usable, Effective Error Messages   (PDF)

'Memory requests for some applications may be denied.' 'Error 404: File not found.' 'Invalid entry. Check your info and resubmit.' 'Fatal error. Procedure aborted.' It's often easy to identify what kinds of error messages don't help users, but it can be tricky to avoid them, and even more of a challenge to create the opposite: error messages that give users a clear indication of the problem, offer information to help them fix it, and provide tips on how to avoid the same situation in the future. This paper details the steps involved in creating understandable, helpful error messages, and suggests ways of communicating the value of good error messages to managers and executives.

Wilska, Emily. STC Proceedings (2004). Articles>Documentation>Help>Online

49.
#24729

On Help Systems In General   (PDF)

In the eras of Windows 3.x and earlier versions of Windows 95, the only help system people worked with or even knew about was WinHelp. Problems started with the transition to Windows 95, when developers and users alike had to learn to deal with WinHelp 4.0's separate dialog with the Contents, Index, and Find tabs.

Liske, David E. MVPs.org (2003). Articles>Documentation>Online>Help

50.
#20748

Online Help: You Think It's Documentation but Your Company Thinks It's Software   (PDF)

As help systems become more complex, integrating text with multimedia, scripting languages, search engines, etc., the line between documentation development and software development blurs. Some companies, especially those that have to adhere to federal or ISO-regulated procedures, are starting to look at online help as a product with its own development needs. This shift is changing the online help from documentation into software, subjecting it to the same controls and processes. This paper looks at how one company is handling this transition.

Rupel, Roberta A. and Peggy Schillinger. STC Proceedings (1999). Articles>Documentation>Online>Help

 
« PREVIOUS PAGE  |  NEXT PAGE »

There are 9 readers currently online: 0 registered users and 9 guests. Register.Follow us on: TwitterFacebookRSSPost about us on: TwitterFacebookDeliciousRSSStumbleUpon