how Great Technical Writing Improve Your Readers Access With A Visual Index

Individuals are visual animals. They take a gander at your item, and see, for instance, a button or show. They need to learn about that control or marker. A Visual Index is a straightforward however strong record access instrument that empowers your Readers to observe their desired data. This article portrays the Visual Index idea and advises how to make one for your report. A VISUAL INDEX A Visual Index is an image of your item or cycle with connections to the important data in the connected report. Utilizing a Visual Index, your Readers can take a gander at the image, and as soon as possible leap to the spot in your archive that depicts the thing of interest. Your record might incorporate a few Visual Indexes (the plural of "file' is "files" not "lists"). Begins WITH A PICTURE The Visual Index begins with an image of your item or interaction. There are different sorts of pictures to utilize, in view of the item type: * Actual Product (for instance, a grill or video plate recorder) Photos of the item (all important perspectives). * A Procedure or Process: A flowchart of the means and choices in the methodology or interaction. * Programming Product 1: Screenshots of the product. * Programming Product 2: Before and after pictures of the work that the item does. * Association: An association graph. Name THE PICTURE Mark every one of the User-Product Interaction Points (U-PIP) on the image. A U-PIP is anyplace that your User and the item might collaborate. U-PIP's incorporate controls, shows, and applicable actual elements of the item (like handles, hooks, and so forth) Give a significant (to your Reader) (name) for the U-PIP. (Utilize that equivalent precise name wherever you allude to that U-PIP.) Aside: If your item utilizes sounds to illuminate the User, then, at that point, incorporate a table of those sounds, what they mean, and a connection into the important region of your archive (depicting the sound). Connect THE U-PIP's TO YOUR DOCUMENT So far, the Visual Index is very much like any all around named image of your item or interaction. Be that as it may, when you add joins into your report, the very much marked picture turns into a Visual Index. The connection ought to be to a part of your archive that you accept your peruser would most need to reach to get the data about that U-PIP. (This is a major inquiry at whatever point you make a list: "does my peruser need to arrive at this spot in my record for this thing?") Your technique for adding connections to the image relies on the distributing system for the archive. In the event that the archive is distributed as: * A Printed archive, then, at that point, use page numbers for the connections; * An Electronic Document, then, at that point, use hyperlinks that a Reader can tap on to follow. On the off chance that the record is distributed as HTML, the visual file can be a picture map. Model 1: A PAIN IN MY FOOT I have an aggravation in my foot when I walk. Assuming I go to a site about feet, it would be exceptionally effective for learning about my torment, on the off chance that I could see an image of a foot with different regions where the aggravation could be. Joins from the foot regions to explicit site pages would empower me to observe the data about my particular foot torment rapidly. Model 2: PHOTO CORRECTING SOFTWARE Show an image with the blunders that your product can deal with, when rectification. Here the U-PIP's are every one of the photograph blunders. Model 3: A COURSE ON WRITING USER DOCUMENTATION The Visual Index is a flowchart for making the User Document. Since the Course is introduced in HTML, the Visual Index is produced using a picture map, with hyperlinks into the areas of the Course applicable to every thing in the flowchart. A Visual Index is a straightforward idea. Be that as it may, in the same way as other basic ideas it is exceptionally strong. Attempt to remember one for your next record. You'll do your Reader an extraordinary help.