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:

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

Microsoft, other rivals slam Google Chrome OS

Intel Linux Graphics Shine With Fedora 12

Editor's Note: Do It Yourself "Cloud"

Google Chrome OS: First looks, first impressions




Arcsight Engineer
The Computer Merchant, Ltd
US-DC-Washington

Justtechjobs.com Post A Job | Post A Resume
:Yet More Tips For Documentation Writers (Writing For Money!)
Yet More Tips For Documentation Writers (Writing For Money!)
Dec 13, 2008, 04 :32 UTC (0 Talkback[s]) (3236 reads)

(Other stories by Carla Schroder)

"The dive right into the hands-on; give readers something to do right away with minimal exposition. Wrap up with more detailed explanations of theory and concepts, and references to additional material.

"Keep articles narrowly focused--don't try to cram too much into a single piece. It's better to address a small task in detail than to cover a lot of ground too shallowly. You can always turn a long, complex topic into a series of nice bite-sized chunks.

"Your readers will adore you if you don't shy away from the hard parts. If you find yourself wanting to write "see the man page for details" instead of outlining the steps yourself, take another look and see if you're trying to take the easy way out. The only place "see foo for more information" belongs is at the end in an additional references section."

Complete Story

Related Stories:
More Tips For Documentation Writers (You Too, Ace Coders)(Dec 10, 2008)
Tips For Documentation Writers (This Means You Too, Ace Coders)(Dec 04, 2008)
Testing Grails: Squash Bugs and Build Executable Documentation(Oct 17, 2008)
The Open Source Principles of Participation(Sep 13, 2008)
Editor's Note: Chrome Comic Books, Yugos, Our New Global Overlords(Sep 05, 2008)
Learning Doxygen for Source Code Documentation(Aug 06, 2008)



No talkbacks posted.
  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