<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
	<title>WritersUA</title>	<link>http://tc.eserver.org/publisher/WritersUA</link>
	<description>A listing of works published by WritersUA 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>WritersUA</title>
		<link>http://tc.eserver.org/dir/WritersUA</link>
	</image>
	<item>
		<title>Review of Screen Capture Tools</title>
		<link>http://tc.eserver.org/34912.html</link>
		<guid>http://tc.eserver.org/34912.html</guid>
		<description>This article describes the process of capturing screens and reviews some of the leading capture tools available. It is revised annually to take account of new releases, and was last updated in February 2009.</description>
	</item>
	<item>
		<title>The WritersUA 2009 Salary Survey</title>
		<link>http://tc.eserver.org/33809.html</link>
		<guid>http://tc.eserver.org/33809.html</guid>
		<description>A central element of any job we hold is the compensation we receive. While compensation is only one factor in our descision to accept a position, it&apos;s how many of us keep score and the way all of us pay the bills. The WritersUA Salary Survey provides you with detailed and comprehensive information about compensation for user assistance professionals. Our 2009 Salary Survey results were viewed on our web site by over 21,000 visitors. We hope you find these new survey results useful in gauging where you stand amongst your peers.</description>
	</item>
	<item>
		<title>An XML Architecture for Technical Documentation: The Darwin Information Typing Architecture (DITA)</title>
		<link>http://tc.eserver.org/33730.html</link>
		<guid>http://tc.eserver.org/33730.html</guid>
		<description>DITA is an architecture for creating topic-oriented, information-typed content that can be reused and single-sourced in a variety of ways. It is also an architecture for creating new information types and describing new information domains, allowing groups to create very specific, targeted document type definitions using a process called specialization, while at the same time reusing common output transforms and design rules. We discuss several methods that can be used to extend DITA&apos;s basic topic types.</description>
	</item>
	<item>
		<title>The WritersUA 2008 Skills and Technologies Survey</title>
		<link>http://tc.eserver.org/33623.html</link>
		<guid>http://tc.eserver.org/33623.html</guid>
		<description>There is no question that the software development world offers a lot of excitement and challenging work. In the area of software user assistance we are particularly challenged by having to master a wide range of disciplines. From foundation skills like writing and editing—to the coding of content—to usability testing and user interface design, we find ourselves in a profession that is difficult to define. What is it that we really do? The objective of this survey is to take a snapshot of our collective professional life in an attempt to identify what we value in our daily work as user assistance professionals.</description>
	</item>
	<item>
		<title>Editing Modular Documentation: Some Best Practices</title>
		<link>http://tc.eserver.org/32036.html</link>
		<guid>http://tc.eserver.org/32036.html</guid>
		<description>Much has been said about the creation of modular documentation - from content management systems, to information architecture, to delivery forms, to the usability of modular content (content being easier to use, easier to understand, and easier to find), and so on. However, not much has been said about the editing of that content, and what the editor&apos;s role is in such an environment.</description>
	</item>
	<item>
		<title>Integrating Partner Information Using XML and XSL</title>
		<link>http://tc.eserver.org/28775.html</link>
		<guid>http://tc.eserver.org/28775.html</guid>
		<description>Having learned that two of these database companies already used single-source files for their error messages, BMC Software integrated the information about the error messages from the database companies. We accomplished our goal by negotiating with our partner companies for the source files of the error message information. This session discusses how we took those source files and modified them to create simple XML files, then transformed them into HTML using XSL transforms within a BMC Software product.</description>
	</item>
	<item>
		<title>XML Architecture for Customized User Assistance</title>
		<link>http://tc.eserver.org/28263.html</link>
		<guid>http://tc.eserver.org/28263.html</guid>
		<description>Content reuse enables technical communicators to create multiple deliverables from a single set of source documents. A key component of reuse is identifying which information belongs in which deliverable. Some customization is feasible with build tags (RoboHelp), conditional text (FrameMaker), topic reuse (FrameMaker and AuthorIT), and similar features.</description>
	</item>
	<item>
		<title>Migrating from HTML to XHTML and XML - Part I</title>
		<link>http://tc.eserver.org/27673.html</link>
		<guid>http://tc.eserver.org/27673.html</guid>
		<description>This is the first part of a two-part article describing a detailed methodology for migrating HTML files to the structure and flexibility of XHTML and/or XML. By using XHTML to add structure and separate content from presentation, you&apos;ll be better positioned for a move to XML. Even if you never move to XML, your XHTML files will be easier to create and maintain, and will be more accessible.</description>
	</item>
	<item>
		<title>Review of Cladonia Exchanger XML Editor</title>
		<link>http://tc.eserver.org/27672.html</link>
		<guid>http://tc.eserver.org/27672.html</guid>
		<description>This article is a review of the Exchanger XML Editor version 3.2 from the Cladonia company. Being such a broad field, the XML Editor category is necessarily far-reaching, and can cover both database management systems and authoring tools. For this reason, this review narrows the scope by looking at the suitability of Exchanger for use by technical communicators and Help authors to create and edit manuals, user guides and Help systems. Much of the focus of this article is therefore on the software&apos;s suitability for DocBook or DITA authoring, and its appropriateness for users without coding skills.</description>
	</item>
	<item>
		<title>WritersUA Salary Survey</title>
		<link>http://tc.eserver.org/27671.html</link>
		<guid>http://tc.eserver.org/27671.html</guid>
		<description>A central element of any job we hold is the compensation we receive. While compensation is only one factor in our descision to accept a position, it&apos;s how many of us keep score and the way all of us pay the bills. The WritersUA Salary Survey provides you with detailed and comprehensive information about compensation for user assistance professionals.</description>
	</item>
	<item>
		<title>Constructing a One-Stop &quot;Answer Station&quot; Website for Software Users</title>
		<link>http://tc.eserver.org/27658.html</link>
		<guid>http://tc.eserver.org/27658.html</guid>
		<description>The web allows us to easily provide updated documentation to our users, but why stop there? There is more to making users successful quickly than just providing documentation. By creating a complete &apos;Answer Station&apos; that is accessible from the application or product, we can not only direct users to that updated documentation, but we can also provide information about technical support, consulting, training, sales, etc.&#xD;&#xD;This article discusses writing a proposal for an Answer Station, determining content, working with other departments to gather information, designing the site, making that design work with an existing corporate website, dealing with tool issues, and finally, going live.</description>
	</item>
	<item>
		<title>Creating &quot;Smart Help&quot; with Conditional Content</title>
		<link>http://tc.eserver.org/27649.html</link>
		<guid>http://tc.eserver.org/27649.html</guid>
		<description>Discusses several methods for making Web-based Help systems &apos;smart,&apos; by using conditional content to customize the appearance and behavior of your pages to the users&apos; needs.</description>
	</item>
	<item>
		<title>Design Checklists for Online Help</title>
		<link>http://tc.eserver.org/27651.html</link>
		<guid>http://tc.eserver.org/27651.html</guid>
		<description>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.</description>
	</item>
	<item>
		<title>Designing and Writing to Reduce User Errors</title>
		<link>http://tc.eserver.org/27653.html</link>
		<guid>http://tc.eserver.org/27653.html</guid>
		<description>A vast majority of documents (I consider print and online as documentation) often works to define the optimized error-free method of performing a task and provides a user with a straightforward solution. However, the user expects documentation to help solve problems and address errors. Thus, attention must be paid to potential problems users can have and how to correct them. Errors have different causes; the information designer should understand the potential types of errors since properly addressing each type requires a different approach in the design and documentation.</description>
	</item>
	<item>
		<title>Determining When to Use Show-Me Helps and Demos</title>
		<link>http://tc.eserver.org/27645.html</link>
		<guid>http://tc.eserver.org/27645.html</guid>
		<description>The availability of powerful yet easy-to-use multimedia tools enables technical writers to consider a powerful new form of embedded user assistance: show-me help. This paper provides an overview of who is currently using show-me help--some current research, some history, and some definitions. It offers some guidance in choosing tools, designing show-me help, and deciding when to include then, concentrating on consideration of your users, potential topics, subsequent releases, and translation. It also suggests how show-me helps can be reused as part of product education and single-sourced into user assistance from the Web.</description>
	</item>
	<item>
		<title>FrameMaker: Structured or Unstructured?</title>
		<link>http://tc.eserver.org/27656.html</link>
		<guid>http://tc.eserver.org/27656.html</guid>
		<description>At the 2004 WritersUA and STC Conferences, structured FrameMaker and XML were among the more popular session topics. There is obviously significant interest in the user assistance community about authoring XML documents with structured FrameMaker. This is not surprising, as many organizations are struggling with the problems of creating and delivering increasing amounts of user assistance in multiple formats, and managing their content in a way that maximizes their capabilities to reuse content across multiple publications.</description>
	</item>
	<item>
		<title>The Future of Indexing?</title>
		<link>http://tc.eserver.org/27641.html</link>
		<guid>http://tc.eserver.org/27641.html</guid>
		<description>A recent article in the Society for Technical Communications&apos; Intercom magazine proclaimed that indexing is on the rise (Seth Maislin, &quot;The Indexing Revival,&quot; February, 2005), and that there is a renaissance of work in the field. But at the WritersUA March Conference, Microsoft&apos;s Longhorn features session declared that Longhorn&apos;s Help system will not contain an index, because &quot;no one uses it.&quot; Then, to add to the discussion, at that same conference Apple revealed that their next help engine will include synonym rings and will add a form of indexing back into their display. Who&apos;s right? Who&apos;s correctly predicting the trends?</description>
	</item>
	<item>
		<title>The Future of RoboHelp?</title>
		<link>http://tc.eserver.org/27646.html</link>
		<guid>http://tc.eserver.org/27646.html</guid>
		<description>The RoboHelp help authoring tool is now entering its thirteenth year of existence. That&apos;s a remarkably long existence for any software title. In that time period, we have seen an amazing expansion of the software industry throughout the 1990s and an equally amazing retraction due to the bursting of the Internet bubble. Making its start in the tiny offices of Blue Sky Software in LaJolla, California, RoboHelp grew into an extremely profitable product. It is also a market leader—having capturing some two-thirds of all Help authoring tool sales. During the Internet bubble years the company changed its name to eHelp, but RoboHelp continued to be its flagship profit center. In 2003, eHelp (and RoboHelp) were acquired by one of the leading providers of web tools—Macromedia. Now it appears that the end may be approaching for RoboHelp.</description>
	</item>
	<item>
		<title>Non-Fatal Errors: Creating Usable, Effective Error Messages</title>
		<link>http://tc.eserver.org/27654.html</link>
		<guid>http://tc.eserver.org/27654.html</guid>
		<description>It&apos;s often easy to identify what kinds of error messages don&apos;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.</description>
	</item>
	<item>
		<title>Online Communities for User Assistance Professionals</title>
		<link>http://tc.eserver.org/27657.html</link>
		<guid>http://tc.eserver.org/27657.html</guid>
		<description>Online communities have become a very valuable source of assistance for answering questions unique to our industry. This article provides an introduction to online communities and describes how to access a few of the most useful sites.</description>
	</item>
	<item>
		<title>Outsourcing Documentation Development: Assessing the Offshore Option</title>
		<link>http://tc.eserver.org/27643.html</link>
		<guid>http://tc.eserver.org/27643.html</guid>
		<description>This paper discusses some of the aspects that should be considered when evaluating the required resources and total cost of offshoring documentation development. As consultants to the documentation industry, The Integrity Group is committed to recommending the overall best solution for each business need. We have, therefore, drawn some conclusions from our research and made recommendations for those who are considering offshoring.</description>
	</item>
	<item>
		<title>Problems in Navigating Online Help: Clues from User Search Patterns</title>
		<link>http://tc.eserver.org/27642.html</link>
		<guid>http://tc.eserver.org/27642.html</guid>
		<description>The largest problem our participants had in using the help system wasn&apos;t in processing the procedural information in the help, but rather finding the correct help topic, a topic generally unaddressed in the literature on how to write a help system. Specifically, participants had difficulty in searching for topics because their terminology differed from the terminology used by the help system, and they became lost in the unclear structure of the system.</description>
	</item>
	<item>
		<title>Putting the &quot;Technical&quot; in &quot;Technical Writer&quot;</title>
		<link>http://tc.eserver.org/27655.html</link>
		<guid>http://tc.eserver.org/27655.html</guid>
		<description>By becoming more technical, you can interact more efficiently with software developers and qualify for a greater variety of software documentation projects. This article outlines ways to learn more about three prevalent technologies: programming languages, databases, and Web server technologies.</description>
	</item>
	<item>
		<title>Review of Screen Capture Tools</title>
		<link>http://tc.eserver.org/27644.html</link>
		<guid>http://tc.eserver.org/27644.html</guid>
		<description>Describes the important attributes of a capture tool and examines and compares the features of five popular products.</description>
	</item>
	<item>
		<title>Stairway to Expertise</title>
		<link>http://tc.eserver.org/27648.html</link>
		<guid>http://tc.eserver.org/27648.html</guid>
		<description>Tools like Captivate, Camtasia, and TurboDemo make it possible for teachers and communicators to create effective software simulations--without programming. Even simple presentation tools, such as PowerPoint can create truly interactive simulations.</description>
	</item>
	<item>
		<title>Tips and Techniques for Single-sourcing with RoboHelp X5</title>
		<link>http://tc.eserver.org/27652.html</link>
		<guid>http://tc.eserver.org/27652.html</guid>
		<description>RoboHelp now offers a rich set of features for delivering multiple customized outputs out of a single project. This article by Matthew Ellison provides some guidelines and tips on using the key single-sourcing features.</description>
	</item>
	<item>
		<title>Trends and Opportunities in Software User Assistance: Part 1</title>
		<link>http://tc.eserver.org/27650.html</link>
		<guid>http://tc.eserver.org/27650.html</guid>
		<description>This article provides an overview of the latest trends in software user assistance based on surveys, interviews, and observations by the author and other experienced user assistance professionals. The article defines the key terminology, highlights the most important issues and elements, and offers both short and long-term predictions for the field. The article will appear in four installments. The next installment will be in February.</description>
	</item>
	<item>
		<title>XML Architecture for Customized User Assistance</title>
		<link>http://tc.eserver.org/27647.html</link>
		<guid>http://tc.eserver.org/27647.html</guid>
		<description>To create a specific deliverable, you collect all of the relevant topics and wrap information around them. A printed book, for instance, contains topics grouped into chapters along with front and back matter.</description>
	</item>
	<item>
		<title>Migrating from HTML to XHTML and XML - Part II</title>
		<link>http://tc.eserver.org/27639.html</link>
		<guid>http://tc.eserver.org/27639.html</guid>
		<description>This is the second part of a two-part article describing a detailed methodology for migrating HTML files to the structure and flexibility of XHTML and/or XML.</description>
	</item>
	<item>
		<title>An XML Architecture for Technical Documentation: The Darwin Information Typing Architecture</title>
		<link>http://tc.eserver.org/27640.html</link>
		<guid>http://tc.eserver.org/27640.html</guid>
		<description>DITA is an architecture for creating topic-oriented, information-typed content that can be reused and single-sourced in a variety of ways. It is also an architecture for creating new information types and describing new information domains, allowing groups to create very specific, targeted document type definitions using a process called specialization, while at the same time reusing common output transforms and design rules. We discuss several methods that can be used to extend DITA&apos;s basic topic types.</description>
	</item>
	<item>
		<title>Microsoft &quot;Longhorn&quot; Help Highlights</title>
		<link>http://tc.eserver.org/21040.html</link>
		<guid>http://tc.eserver.org/21040.html</guid>
		<description>Microsoft’s specification for &apos;Longhorn&apos; Help represents a major revolution in user assistance development for the Windows platform. Instead of simply refining the technical infrastructure of Help (windowing, links, search, etc.), Microsoft has given a good deal of thought to the needs of both Help authors and end-users.</description>
	</item>
	<item>
		<title>User Assistance Resource Directory: Web Resources</title>
		<link>http://tc.eserver.org/20886.html</link>
		<guid>http://tc.eserver.org/20886.html</guid>
		<description>The following general resources are Web sites of interest to Help authors, technical communicators, and programmers.</description>
	</item>
	<item>
		<title>A Review of RoboHelp Office 2002</title>
		<link>http://tc.eserver.org/20033.html</link>
		<guid>http://tc.eserver.org/20033.html</guid>
		<description>This is the first in a series of articles that builds into a personal review of RoboHelp Office 2002. This first article introduces the new release and discusses Topic Templates, Headers and Footers, and the new MS Word Import capability.</description>
	</item>
	<item>
		<title>A Mixed Bag of Job Prospects for Tech Writers</title>
		<link>http://tc.eserver.org/19649.html</link>
		<guid>http://tc.eserver.org/19649.html</guid>
		<description>One of the areas the 2001 ITAA survey looks at is supply and demand. Of the estimated 258,332 jobs that IT hiring managers predict they will add this year, only 1,799, or less than 1%, are for tech writers. This is down a whopping 91% from the year 2000 where the 20,773 available tech writer jobs accounted for almost 5% of the total. The news may not be as bad as it sounds. On the supply side, there is an expected shortfall of 1,008 qualified candidates in filling the open tech writer jobs.</description>
	</item>
	<item>
		<title>Ten Practical Techniques for Single-Sourcing with FrameMaker</title>
		<link>http://tc.eserver.org/14083.html</link>
		<guid>http://tc.eserver.org/14083.html</guid>
		<description>A PowerPoint slide show about using FrameMaker for single-source document creation and management.</description>
	</item>
	<item>
		<title>Adding User Annotations to Help Topics</title>
		<link>http://tc.eserver.org/13775.html</link>
		<guid>http://tc.eserver.org/13775.html</guid>
		<description>This article discusses a feature called User Annotations, whereby users can add their own custom notes to Help topics, and presents a method for implementing it in web pages or in HTML Help topics.</description>
	</item>
	<item>
		<title>Just Say &quot;Help&quot;: Implementing Help in VoiceXML</title>
		<link>http://tc.eserver.org/13773.html</link>
		<guid>http://tc.eserver.org/13773.html</guid>
		<description>One of the exciting aspects of XML is the number of ways it is being used to provide new means of communicating and gathering new information. One such use is VoiceXML, an emerging W3C standard that brings voice to the Web or the Web to the phone.</description>
	</item>
	<item>
		<title>A Usability Test of Web-based User Assistance</title>
		<link>http://tc.eserver.org/13774.html</link>
		<guid>http://tc.eserver.org/13774.html</guid>
		<description>Recently, WinWriters used the web-based registration process for its annual Online Help Conference as a case study to test several models of user assistance for the Web. We conducted a series of usability tests to: find out how what sort of questions and problems users have as they complete a web-based transaction; discover how users respond to various forms of user assistance available within a web-based task; define the registration process for future conferences. The tests provided some clear conclusions as to user preferences. We have described the tests and summarized the findings here.</description>
	</item>
	<item>
		<title>WinWriters Online Help Resource Directory</title>
		<link>http://tc.eserver.org/13776.html</link>
		<guid>http://tc.eserver.org/13776.html</guid>
		<description>This comprehensive, up-to-date list is your one-stop link to the brightest and best resources in the Help world—all the tools, contacts, and information you&apos;ll need to develop thorough, effective, polished Help projects.</description>
	</item>
	<item>
		<title>WritersUA (formerly WinWriters)</title>
		<link>http://tc.eserver.org/10157.html</link>
		<guid>http://tc.eserver.org/10157.html</guid>
		<description>WinWriters specializes in providing quality training and publications for the community of online Help developers. Our clients represent a diverse group of technical writers, software developers, contractors, and consultants—all of whom share a common interest in online Help. WinWriters is the premier source for world-class, world-wide Help development conferences and seminars. The annual WinWriters Online Help Conference draws hundreds of participants to hear the latest news, techniques, and technologies in the Windows Help arena. Our Help training seminars are held in high regard throughout the U.S. and the world.</description>
	</item>
	<atom:link href="http://tc.eserver.org/publisher/WritersUA.xml" rel="self" type="application/rss+xml"/>
</channel>
</rss>