http://tc.eserver.org/publisher/Answers_for_All A listing of works published by Answers for All in the field of technical communication. en-us Copyright (c) 2005-08 by the EServer. All rights reserved. tclib-editorial@eserver.org (TC Library Editorial Board) webmaster@eserver.org (Geoffrey Sauer) http://tc.eserver.org/images/newlogo.gif http://tc.eserver.org/dir/Answers_for_All http://tc.eserver.org/35494.html http://tc.eserver.org/35494.html I’m amazed when I hear people say they learn nothing from others in the technical communication field. Some people have a lot of experience, so they feel there are few opportunities to learn from others. I believe they forget that often through discussions, we discover a new perspective or a new way to solve an old problem. Different approaches can also lead to new techniques and solutions. http://tc.eserver.org/35445.html http://tc.eserver.org/35445.html How is the role of technical communicators changing? What skills should we be focused on for future success? With content coming from many sources and contributors throughout the community, technical communicators can feel threatened. For many years, we were the sole developers of content, carefully crafting each phrase to deliver information clearly and concisely. As social media expands, our skills for crafting the message may become less important and less valued. http://tc.eserver.org/34714.html http://tc.eserver.org/34714.html Embedded user assistance is only part of a complete documentation plan. It does not replace the need for other types of content. For example, embedded user assistance is not a good delivery mechanism for comprehensive concepts and detailed discussions of a topic with strategy and best practice guidelines. However, with a strong design, embedded user assistance can support the immediate needs of the user and provide a valuable, contextual link that steers the user into the other parts of the documentation as needed. http://tc.eserver.org/34715.html http://tc.eserver.org/34715.html Technical Communication continues to change as we find new ways to meet the needs of our audiences. I have attended several conferences recently and discussed several of the latest trends with other technical communicators. This article provides a quick list of several of these trends and ideas. http://tc.eserver.org/34010.html http://tc.eserver.org/34010.html Much in the same way that Microsoft Word and PageMaker made desktop publishing more widely available and eliminated the need for tagging to achieve formatting, blogs and wikis are doing the same for the web. You can use WordPress to create an entire web site without knowing or using HTML. Editme.com is providing web site services using wiki technologies. These tools help users publish content with less knowledge of the underlying tagging. http://tc.eserver.org/33636.html http://tc.eserver.org/33636.html Software products have found ways to share content and reuse content to deliver more value with limited resources. For example, fantasy football web sites share player news, injury reports, and game statistics. Security products often reuse security announcements and warnings from trusted sources, and present them as rebranded content. We are also seeing software vendors using Twitter and RSS feeds to distribute information and announcements. The next step is when these information feeds are integrated into the product user interface itself, making it the one stop resource for all the information needs of its users. No more need to use google when your product itself delivers the answers to all your questions from the sources you trust. http://tc.eserver.org/33602.html http://tc.eserver.org/33602.html With the move to XML, DITA, and other new standards, the entry cost for new tools is lower relative to established tools like Word and FrameMaker, since all tools need to invest to implement these new standards. New workflows are emerging in some cases, such as topic-based authoring and shared content, which give new tools a distinct advantage. The new tools can start with the new paradigm, rather than trying to migrate existing content and provide “backward” compatibility. http://tc.eserver.org/33327.html http://tc.eserver.org/33327.html For those of us who communicate technical content for a living, we share many job titles, such as technical writer, information developer, technical communicator, multimedia engineer, content developer, and many others. Without one focused set of titles, how did we know this is what we wanted to do?