<?xml version="1.0" encoding="UTF-8"?> <rss
version="2.0"
xmlns:content="http://purl.org/rss/1.0/modules/content/"
xmlns:wfw="http://wellformedweb.org/CommentAPI/"
xmlns:dc="http://purl.org/dc/elements/1.1/"
xmlns:atom="http://www.w3.org/2005/Atom"
xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
> <channel><title>Five Free Apps &#187; writing</title> <atom:link href="http://www.fivefreeapps.com/category/writing/feed" rel="self" type="application/rss+xml" /><link>http://www.fivefreeapps.com</link> <description>Covering the Best in Apps &#38; So Much More</description> <lastBuildDate>Sun, 12 Feb 2012 12:31:41 +0000</lastBuildDate> <language>en</language> <sy:updatePeriod>hourly</sy:updatePeriod> <sy:updateFrequency>1</sy:updateFrequency> <generator>http://wordpress.org/?v=3.3.1</generator> <item><title>Tips To Improve The Appearance Of A Technical Document</title><link>http://www.fivefreeapps.com/2012/02/tips-to-improve-the-appearance-of-a-technical-document.html</link> <comments>http://www.fivefreeapps.com/2012/02/tips-to-improve-the-appearance-of-a-technical-document.html#comments</comments> <pubDate>Sun, 12 Feb 2012 12:26:42 +0000</pubDate> <dc:creator>Brian Mongold</dc:creator> <category><![CDATA[blogging]]></category> <category><![CDATA[guest author]]></category> <category><![CDATA[tech]]></category> <category><![CDATA[writing]]></category> <category><![CDATA[how-to]]></category> <category><![CDATA[technical writing]]></category> <category><![CDATA[tips]]></category> <guid
isPermaLink="false">http://www.fivefreeapps.com/?p=9489</guid> <description><![CDATA[<p
style="text-align: justify;">Most companies spend a lot of time and money to hire copywriters and media specialists to make visually appealing advertisements. User manuals, product maintenance instructions and other technical documentation, which can impact the user&#8217;s experience with the product are left to the engineers, often without any significant involvement even of the product sales [...]]]></description> <content:encoded><![CDATA[<p
style="text-align: justify;">Most companies spend a lot of time and money to hire copywriters and media specialists to make visually appealing advertisements. User manuals, product maintenance instructions and other technical documentation, which can impact the user&#8217;s experience with the product are left to the engineers, often without any significant involvement even of the product sales or support teams.</p><p
style="text-align: justify;">All of us have come across examples of jargon filled technical documentation where we have to search to find the information we need. These documents also tend to be poorly produced. For example, a mobile phone user manual is often printed on a booklet of the size of the phone, making the font size difficult to read and the sketches impossible to understand. A car maintenance manual does not recognize that it would get handled with greasy hands when the car user has a problem.</p><p
style="text-align: justify;">A few simple tips could help improve the appearance of a technical document.</p><p
style="text-align: justify;"><strong>Make the document specific to the reader</strong></p><p
style="text-align: justify;">The technical document should be written with the reader firmly in mind. The user manual for an appliance will have both first time users and people who have used similar appliances in the past. It would be a good idea to include a separate section for first time users that an informed user can skip.</p><p
style="text-align: justify;">The material should be written in short simple sentences, containing no more than 8 to 10 words per sentence. Longer sentences are more difficult to understand. Use simpler words. Avoid the use of overly technical terms or acronyms. Where these are unavoidable, explain what these are the first time you use them in the text. Use only one term throughout the document. If you substitute one term with a synonym, the user may not recognize that you mean the same item.</p><p
style="text-align: justify;"><strong>Make the document visually attractive</strong></p><p
style="text-align: justify;">A crowded document filled with dense text makes for difficult reading. An important requirement for a visually appealing document is to use lots of white space. The margins should be adequate on all sides. The right font size and line spacing can help improve appearance of the document. Align only the start of each line of text, leaving the end spaces to vary naturally with word length in the text.<img
class="alignright  wp-image-9490" title="Technical Writing Tips" src="http://www.fivefreeapps.com/wp-content/uploads/2012/02/Technical-Writing-Tips.jpg" alt="Technical Writing Tips Tips To Improve The Appearance Of A Technical Document" width="290" height="200" /><br
/> The text should be broken up into paragraphs with sub-headings. Each of these paragraphs should contain one core idea and should be written to be self-standing. The reader should understand the core idea from that one paragraph without needing to go back and read previous paragraphs.</p><p
style="text-align: justify;">The use of tabulations for select information or bullet points in the text adds to the visual appeal. Important points or messages can be highlighted using italics or bold text. Using capital letters for emphasis makes the text more difficult to read.</p><p
style="text-align: justify;"><strong>Add photographs and sketches</strong></p><p
style="text-align: justify;">The old saying &#8220;A picture is worth a thousand words&#8221; applies to technical documentation. Adding a photograph or sketch makes it easy to communicate. Research has shown that the human eye gets drawn first to a photograph or sketch in a document page before the printed text.</p><p
style="text-align: justify;">The photographs need to illustrate the specific point being explained in the accompanying text. General product photographs may not add value. The same applies to sketches. Reproducing an engineering drawing with too many details or having unnecessary dimensions and notes simply confuses the reader.</p><p
style="text-align: justify;">Good technical documentation adds to the user experience with the product and deserves greater attention. Poor documentation can leave the impression of a poorly made product. Well made technical documentation can help reduce the number of product complaints or service calls.</p><div
style="text-align: justify;"><strong>About the author</strong>: Margaret is a blogger by profession. She loves writing on design and technology. Beside this she is fond of books. She recently bought a  <a
href="http://www.bornrich.com/entry/shape-shifting-cay-sofa-alexander-rehn/">Sofa Design</a>. These days she is busy in writing an article on <a
href="http://www.ecofriend.com/entry/big-question-vertical-farms-food-shortage/">vertical farming</a>.</div><div
style='clear:both'></div>]]></content:encoded> <wfw:commentRss>http://www.fivefreeapps.com/2012/02/tips-to-improve-the-appearance-of-a-technical-document.html/feed</wfw:commentRss> <slash:comments>0</slash:comments> </item> </channel> </rss>
