A directory of resources inthe field of technical communication.

Documentation

526-549 of 1,527 found. Page 22 of 62.

About this Site | Advanced Search | Localization | Site Maps
 

« PREVIOUS PAGE 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25  NEXT PAGE »

Extreme documentation is an agile methodology for developing documentation in small to medium-sized teams in the face of vague or rapidly changing requirements.

 

526.
#19125

A Good Installation Guide Increases User Satisfaction and Reduces Support Costs   (peer-reviewed)   (members only)

In its first endeavor, the new Customer Documentation Group at SABRE Travel Information Network has shown that it adds value.

Blackwell, C. Al. Technical Communication Online (1995). Design>Documentation>Usability

527.
#19124

A Good User's Guide Means Fewer Support Calls and Lower Support Costs   (peer-reviewed)   (members only)

Good user documentation means fewer client support calls and lower support costs at GE Information Services in Rockville, Maryland.

Spencer, Cathy J. and Diana Kilbourn Yates. Technical Communication Online (1995). Design>Documentation>Usability

528.
#34696

Google Wave Changes Everything You Know About Agile Collaboration and Technical Documentation

Beyond the obvious impact on the Social Web, Google Wave is also going to change aspects of every business that currently relies on communication and collaboration tools of any sort, including the ubiquitous but lowly email.

Greywalker, Shannon. Greyfiti (2009). Articles>Documentation>Social Networking>Collaboration

529.
#29049

Grappling with Distributed Usability: A Cultural-Historical Examination of Documentation Genres Over Four Decades   (peer-reviewed)   (members only)

Traditional models of usability assume that usability is a quality that can be designed into a particular artifact. Yet constructivist theory implies that usability cannot be located in a single artifact; rather, it must be conceived as a quality of the entire activity in which the artifact is used. This article describes a distributed approach to usability, based on activity theory and genre theory. It then illustrates the approach with a four-decade examination of a traffic accident location and analysis system (ALAS). Using the theoretical framework of genre ecologies, the article demonstrates how usability is distributed across the many official and unofficial (ad hoc) genres employed by ALAS users.

Spinuzzi, Clay. Journal of Technical Writing and Communication (2001). Articles>Documentation>Usability>History

530.
#21186

Grassroots Documentation   (PDF)

We often hear how the Web can be used to deliver technical documentation. But have you ever thought about the Web as technical documentation? When dozens, or perhaps hundreds, of people, all using the same product, start posting tips and solutions to problems on different Web sites, the entire Internet becomes a kind of crude users’ manual.

Martin, Maurice. Intercom (2003). Articles>Documentation>Online>Community

531.
#35707

Great Documentation Is Key to Open Source Success

Listen up open source developers, if you want your project to succeed you’re going to have to do more than write great code; you’re going to have to document it, teach new users how it works and provide real-world examples of what you can do with it. That’s the message from Jacob Kaplan-Moss, one of the creators of Django, a very successful open source, Python-based web framework. At least some Django’s success can be attributed to its thorough documentation which is not just reference materials, but also includes tutorials, topical guides and even snippets of design philosophy.

Gilbertson, Scott. Webmonkey (2009). Articles>Documentation>Usability>Open Source

532.
#20787

A Guide for Software Project Managers - Planning User Documentation   (PDF)

A Guide to the Project Management Body of Knowledge (PMBOK® Guide)–2000 Edition is the main sourcebook in the project management field. Whilst it covers Project Communications Management, it doesn't extend to user documentation. This article seeks to provide guidance for project managers as to how the user documentation process fits in with the overall project planning. It examines: the traditional way documentation is approached and how it impinges on project planning the effects of making changes to this traditional approach.

Johnston, Carol. Cherryleaf (2003). Articles>Documentation>Project Management>Body of Knowledge

533.
#33893

Guidelines for Good Sample Code

Sample code often provides the quickest, clearest way to learn how an SDK works. If you have software engineering experience, then you should already know many principles for writing good code. However, what you may not realize is that some of the good practices that you learned for writing good production code do not apply to writing good sample code. Some techniques, such as comments and clear variable names, apply to both production code and sample code. However, there are good reasons to use hard-coded values in sample code, which should be avoided in production code, and there are good reasons to avoid object-oriented designs when writing sample code.

Gruenbaum, Peter. Prestwood (2009). Articles>Software>SDK>Documentation

534.
#38453

The Guilty Pleasure of Writing Policy and Procedure Documents

We have a number of projects running at the moment that involve us improving organisations’ policy and procedures documents. It may not seem likely, but these projects are enormous fun.

Pratt, Ellis. Cherryleaf (2012). Articles>Documentation>Policies and Procedures>Business Communication

535.
#36758

Hacking Author-it Webhelp

Author-It Webhelp output is built using HTML templates (for the layout and structure), CSS (for the styling) and is powered using Javascript. If you are competent in HTML and CSS you can do a lot of tweaking of the templates.

McLean, Gordon. One Man Writes (2010). Articles>Documentation>Help>Author It

536.
#25011

Harnessing the Earthquake: Reaching Group Consensus When Changing the Documentation Process   (PDF)

A causal-analysis session is a problem-solving method that brings groups of people together to jointly solve common problems and make process changes. This method ensures that everyone who will be affected by a process change has the opportunity to provide input and agree to the solution. In large departments, reaching group consensus is a challenge. This paper presents our department's implementation of the causal-analysis method.

Coppola, Carolyn M. and Kristine Logan. STC Proceedings (1994). Articles>Documentation>Collaboration

537.
#28786

Harry Miller on Multimedia Documentation

Miller, a technical editor at Microsoft interested in multimedia documentation, talks about why multimedia documentation is a growing trend and how writers can get started. He discusses Microsoft's Channel 9 and the human element with instructional screen demos.

Miller, Harry and Tom H. Johnson. Tech Writer Voices (2007). Articles>Interviews>Documentation>Multimedia

538.
#35613

The Harsh Truth about Screencasts

If you watch screencasts, you probably have seen some that are just worthless. How long did you stay to watch? Not long, I am sure. Why am I being so critical? Because it is true.

Schoen, Michelle. Virtual Assistant Demo Girl (2009). Articles>Documentation>Video>Screencasting

539.
#32824

Has Anyone Used Your Product

Before you release a product, have some people use it. From these "test users" get solutions to problems, tips and knowledge that would help your real-life Users. Put that information in your User Documentation, and on your product support website.

Great Technical Writing (2008). Articles>Documentation>Technical Writing>User Centered Design

540.
#28540

HAT-Matrix

HAT-Matrix.com is a new representation of an old standard--the Help Authoring Tool (HAT) Comparison Matrix that was available from helpstuff.com for five years (2001-2006). But instead of a static list, this site uses a searchable database. And instead of someone choosing the tools that are included, vendors choose whether to include their tools.

HAT-Matrix (2006). Resources>Documentation>Software>Help

541.
#19715

Help Development:

Too often technical writers fall into the 'tell them everything and tell them all at once' pit. Guided by a well-meaning desire to 'educate' users, what these writers typically do is overwhelm them. Finding the information you need when you need it is a key to success in every business function of every company. Therefore, technical communicators who are able to provide their customers with quick and useful knowledge bring an incredible added value to a beleaguered work force constantly expected to do more and to do it faster.

Edwards, Verlane. STC Central Iowa (2000). Articles>Documentation>Online

542.
#33370

Help for Help files

Normally I like to write positive stuff and I really love Uxmatters.. it’s a great site. BUT, the recent article PDF Manuals: The Wrong Paradigm for an Online Experience from my perspective is pretty much everything that’s wrong with Help today.

Lang, Keith. UI and Us (2008). Articles>Documentation>Writing>Technical Writing

543.
#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

544.
#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

545.
#23118

Help Strategies and Their Effect on Graphical Icon Usage

An increasingly popular component of modern graphical human-computer interfaces are graphical command buttons. Studies have shown that graphical command buttons can enhance user productivity. However, two factors, the time required to acquire a working knowledge of the graphical command set and the need for frequent use to maintain the knowledge limit the effectiveness of graphical command buttons as a user interface strategy. This study attempts to quantify the effects of four types of help (balloon style, a mouse documentation line at the bottom of the screen, a help browser, and hardcopy documentation) on the ability of novice users to acquire a working knowledge of a graphical command set. The study did not find any significant difference (based on the anova and manova tests) between the four treatments.

McAlister, Britt and Chavi Greengart. SHORE (1997). Design>Documentation>Human Computer Interaction>Help

546.
#13673

Help Technologies

A page about each of the major online Help technologies: HTML Help, JavaHelp, WebHelp, WebWorks Help, WinHelp, and WinHelp 2000.

Knopf, David A. Knopf Online. Resources>Documentation>Help

547.
#23326

Help-Site Computer Manuals

A directory of hundreds of examples of online software documentation, categorized and rated by users.

Help-Site. Resources>Documentation>Software

548.
#14213

Help! It's Not Just a Beatles Movie

Windows Help has steadily improved to the point where the Windows XP Help and Support Center provides nearly exhaustive answers to your queries. Here’s how the Help and Support Center works.

Crawford, Sharon. Microsoft (2001). Articles>Documentation>Help

549.
#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

550.
#37390

Help! User Documentation that Works

If you work on a new-concept website—that is, a website that doesn’t follow an established format like an ecommerce site or a blog—producing user documentation might be the last task on your mind. Yet for sites that present processes unfamiliar to users, quality documentation is crucial.

Laidlaw, Georgina. SitePoint (2010). Articles>Web Design>Usability>Documentation

 
« PREVIOUS PAGE  |  NEXT PAGE »

 

Follow us on: TwitterFacebookRSSPost about us on: TwitterFacebookDeliciousRSSStumbleUpon