| |||||||||
|
1. #23799 Ask the Indexer: Get Answers to your Indexing Questions from Experienced Technical Indexers After brief introductions by 4 panelists who are all members of the Indexing SIG (and experienced indexers and technical writers), we plan to discuss Frequently Asked Questions (FAQs) about indexing, and allow plenty of time for questions. Bonura, Larry S., Dick Evans, Joan K. Griffitts and Peg Mauer. STC Proceedings (1999). Articles>Indexing>Technical Editing>FAQ 2. #11852 This site is a concise guide to some of the most commonly violated rules of writing, grammar, and punctuation. It is intended for all writers as an aid in the learning and refining of writing skills. Explore each of the rules to see examples of its application, and use the references to find additional explanations and examples on the Web or in print. Look up grammatical terms in the glossary. For a wider variety of information, check related FAQs and other writing resources. 3. #10134 Linked presentation as we know it today -- a navigation menu, a table of contents, a list of frequently asked questions (FAQ) -- suits informational material such as technical manuals, government documents, and most scientific research papers. These presentation formats do little to enhance narrative forms, however. Most discussion of online narrative -- and most experimentation -- has centered on fiction (Coover, 1993, 2000; Minganti, 1996) and literary studies (Landow, 1992; Lavagnino, 1997). Journalism narratives, especially long-form journalism, are overdue for attention. McAdams, Mindy and Stephanie Berger. Journal of Electronic Publishing (2001). Articles>Publishing>Hypertext>FAQ 4. #22792 Offers advice on creating effective FAQ documents. Hart, Geoffrey J.S. Intercom (2004). Articles>Documentation>Technical Writing>FAQ 5. #30810 Nine Tips for Writing Better FAQs Frequently asked questions, or FAQs, are an important part of your product documentation. Writing well-targeted and thorough FAQs allow users to quickly find the answers they need so they can be more productive when using your product. Here are some tips for writing FAQs that will get your users on track quickly and help reduce Customer Support calls. HelpScribe (2008). Articles>Documentation>Writing>FAQ 6. #13211 Technical Communications and Customer Support: Partnering to Publish What Customers Want to Know Most customers do not provide direct feedback on product documentation. Instead, when documentation fails to provide the information that a customer needs to use a tool effectively, he or she calls Customer Support for advice. To find out what information was missing or incorrect in our product documentation, I analyzed the Cadence Customer Support call logs that pertained to my products to find out what questions customers ask most about each product. I then partnered with teams of applications engineers (AEs) to improve our documentation by answering common questions, both on the Web in FAQ documents and in product manuals. Guglielmetti, Krista. STC Proceedings (2000). Presentations>Documentation>Assessment>FAQ
| |||||||||
| |||||||||
Click here to learn how to embed the RSS feed of this category in your website.