#20391
Apple Help and John Carroll's Minimalism 
This report gives a brief overview of minimalism, a description of an Apple Computer documentation project, and a summary of my findings. It also provides some of my and my Apple colleagues' recommendations to improve both the user's experience and that of the instructional designers working to write Apple Help content. Through the course of this report, I will provide support for my hypotheses that (1) the current Apple Help model is not a minimalist help system, but that (2) users of most Apple software would not be well served by such a system anyway.
Tevenan, Matthew P. University of Washington-Seattle (2002). Books>Documentation>Help>Minimalism
#27898
This book introduces the construction of hard disk, the theory of data saving, construction of file system, the reasons of data lost and the examples of data recovery in detail. This book is easy to understand with a lot of graphs and pictures in it. With the help of it, the general user will never be upset of data lost. It also enable you to become a data recovery expert quickly.
Chengdu Yiwo (2006). Books>Documentation>Technology>Microsoft Windows
#31755
This area provides access to my DITA specialization tutorial and other DITA specialization-related information and materials.
#26372
DocBook provides a system for writing structured documents using SGML or XML. It is particularly well-suited to books and papers about computer hardware and software, though it is by no means limited to them.
#26196
DocBook XSL: The Complete Guide
DocBook is a collection of standards and tools for technical publishing. DocBook was originally created by a consortium of software companies as a standard for computer documentation. But the basic 'book' features of DocBook can be used for other kinds of content, so it has been adapted to many purposes.
Stayton, Bob. Sagehill (2005). Books>Documentation>XSL>DocBook
#26191
This book is designed to be the clear, concise, normative reference to the DocBook DTD. This book is the official documentation for the DocBook DTD.
Walsh, Norman and Leonard Muellner. Docbook.org (2003). Books>Documentation>XML>DocBook
#30813
Microsoft Manual of Style for Technical Publications 
Understanding the user interface can be a confusing experience for customers. By using a consistent set of terminology and style, you can help customers navigate the product user interface successfully. Once customers become familiar with this system, they can jump seamlessly between content about different products.
Microsoft (2004). Books>Style Guides>Technical Writing>Documentation
#29885
An introduction to generating screen captures from Microsoft Windows computers. Consider your deliverables; where is the screen capture going to be used and seen by the customer? This helps you determine how you need to create your screen capture.
Brierley, Sean. TECHWR-L (2002). Books>Documentation>Technical Illustration>Screen Captures
#14144
This document is about making screen captures for technical writers working primarily in a Microsoft Windows environment. The tools targeted include Adobe FrameMaker, Microsoft Word, Adobe Acrobat, along with Techsmith’s SnagIt, Adobe Photoshop, and Ulead’s PhotoImpact 4.2. Certainly, the thoughts and techniques mentioned herein can be applied to other professions, other operating systems, and other tools.
Brierley, Sean. TECHWR-L. Books>Documentation>Image Editing>Screen Captures
#21390
Running a volunteer organization is an opportunity to develop your leadership ability and your sense of professional community. When you complete your duties at the end of this year, you will have gained leadership skills that will benefit you in other areas of your life. This handbook was prepared by STC leaders with many years of experience running local chapters. Their experiences resulted in the wealth of tips, suggestions, and cautions that this document contains. As part of your planning for the year, STC strongly encourages you to take the time to review the entire handbook.
#28539
This site provides additional materials for every chapter and directs students and instructors to the best Web resources available in technical communication.
Markel, Mike. Bedford-St. Martin's (2002). Books>Documentation>Technical Writing
#28360
A Theory of Presentation and its Implications for the Design of Online Technical Documentation
This study proposes a theory of presentation and discusses its implications for the design of online technical documentation. The theory is based on an investigation of how professional service engineers use technical documents relating to the oil system of a commercial aircraft engine. A second source was the design and evaluation of a novel hypermedia document system, the cinegram, which constitutes the practical part of the submission. The cinegram prototype uses animated diagrams and other media to show processes within an aircraft engine’s oil system.
Fischer, Detlev. oturn (1997). Books>Documentation>Online
#19753
Use-Oriented Documentation in Software
We examine how efficiency and quality in software development can be increased through the design of software documentation and reading support for software documentation. The thesis reports on the DJavadoc project and the reading support for online Java API reference documentation that it provides. The Java API reference documentation can be viewed as a collection of documentation designed for multiple needs. As a consequence, excessive information is present in most situations. In DJavadoc we have extended the official Java API reference documentation to achieve control over the visibility of information types. DJavadoc adds client-side, real-time redesign to the documentation to support the design of multiple views. As a result, the reader may further design views of the information that are more in line with the reader’s personal and changing needs. In the thesis we also discuss online API reference documentation and its role in programming.
Berglund, Erik. Linkopings Universitet (1999). Books>Documentation
#34116
GNOME Handbook of Writing Software Documentation
The GNOME Documentation Project (GDP) aims to provide GNOME and GNOME applications with a complete, intuitive, and clear documentation system. At the center of the GDP is Yelp, which presents a unified interface to GNOME-specific documentation as well as other Linux documentation such as man pages and texinfo documents. The GNOME Help System provides a comprehensive view of documentation on a machine by dynamically assembling the documentation of GNOME applications and components which are installed.
Mason, David, Daniel Mueth, Alexander Kirillov, Eric Baudais, Eugene O'Connor and John Fleck. GNOME (2003). Books>Documentation>Software>Technical Writing
