Linux Today: Linux News On Internet Time.
Search Linux Today
search.internet.com
Linux News Sections:  Blog -  Developer -  High Performance -  Infrastructure -  IT Management -  Security -  Storage -
Linux Today Navigation
LT Home
Preferences
Contribute
Link to Us
Search
Linux Jobs

Become a Marketplace Partner

internet.commerce
Be a Commerce Partner














The Linux Channel at internet.com
Linux Today
Enterprise Linux Today
Apache Today
JustLinux.com
Linux Planet
PHPBuilder
All Linux Devices
Technology Jobs

JustTechJobs.com

LinuxToday Newsletters
Subscribe News
Subscribe PR
Subscribe Security

internet.com
IT
Developer
Internet News
Small Business
Personal Technology

Search internet.com
Advertise
Corporate Info
Newsletters
Tech Jobs
E-mail Offers

 






Current Newswire:

Microsoft's embrace of MySQL could kill it

Mastering Grub 2 The Easy Way

Shedding commercial attitudes towards documentation

Will secret copyright treaty restrict your digital rights?

Saving the "Best" for Last - Fedora 12 (Constantine)

LinuxCertified Announces its next Linux System and Network Administration BootCamp

The Problem With The Linux Community

Vim 101: A Beginner's Guide to Vim

Open Source Science: A Revolution From Within

openSUSE 11.2-- Incremental Updates, Plenty of Polish




SiteMinder / Webhosting
The Computer Merchant, Ltd
US-MA-North Quincy

Justtechjobs.com Post A Job | Post A Resume
:More Tips For Documentation Writers (You Too, Ace Coders)
More Tips For Documentation Writers (You Too, Ace Coders)
Dec 10, 2008, 00 :05 UTC (2 Talkback[s]) (2971 reads)

(Other stories by Carla Schroder)

"An unfortunate amount of computer documentation is so terse it seems as though the writer had to pay by the word. While it is possible to over-explain, that's hardly ever a problem. With computers we're dealing mostly in abstract concepts, so don't be shy about spelling out even details that seem too obvious and basic, because to a lot of readers they won't be obvious and basic.

"A picture is worth a thousand words, and so are screenshots showing exactly what you're talking about. For command line programs it's even easier than creating screenshots, just copy and paste the text. You want to be as literal as possible, because computers demand precise literal commands. They can't read your intent or waving hands, only what you type."

Complete Story

Related Stories:
Tips For Documentation Writers (This Means You Too, Ace Coders)(Dec 04, 2008)
Healing the Rift Between Wikipedia and Creative Commons(Nov 04, 2008)
FSF Releases New Version of GNU Free Documentation License(Nov 04, 2008)
The Need to Know: Documentation in Linux(Oct 01, 2008)
The Open Source Principles of Participation(Sep 13, 2008)


Index Mode   |   Flat Mode   |   Thread Mode   |   Thread Flat  
  Talkback(s) Name  and Date
There are a group of us involved with th ...   Writing a manual   
Greg P
Dec 10, 2008, 13:42:07
 
> There are a group of us involved with  ...   Re: Writing a manual   
Carla Schroder
Dec 11, 2008, 01:13:22
 
  Home | Search Talkbacks | Customize View    Top of Page  



Enter your comments below:

* Your Name:

* Your Email Address:

* Subject:

CC: [will also send this talkback to an E-Mail address]

* Comments:

Tags allowed:<I>,<B> and <U>. See our talkback-policy for more about talkback content.

Fields marked with * are required!






..............................




All times are recorded in UTC.
Linux is a trademark of Linus Torvalds.
Powered by Linux, Apache and PHP

internet.commediabistro.comJusttechjobs.comGraphics.com

Search:

WebMediaBrands Corporate Info

Legal Notices, Licensing, Permissions, Privacy Policy.
Advertise | Newsletters | Shopping | E-mail Offers | Freelance Jobs