Help  |   Contact Us  |   About Us  |   News and Events
Books, conferences, and other information about... Moving to Linux Switching to OOo Building Linux Apps Using Visual FoxPro
Buy      Download      Your Account      Catalog      Support      Conferences      Resources      Fun

Resources - Write/Edit for Hentzenwerke

Wanna write or edit a book? Here's all you need to know about how the publishing process works here.

Write/Edit for Hentzenwerke
Writing Whitepapers

A commercial whitepaper has a few attributes that differ from other types of material we've produced in the past (i.e. printed books). This page explains what those attributes are so you know what you're getting into and what to do to write a whitepaper for us.

What is a whitepaper?

I assume that you've already read about whitepapers under the Catalogs link on this site. To come at it from the point of view of an author, a whitepaper is your chance to discuss something that is valuable, but just not long enough for a book by itself. Generally, a whitepaper covers a narrowly focused subject, anywhere from 20 to 100 pages. It may or may not come with source code.

The table of contents

The key aspect of a whitepaper is that it's difficult to explain exactly to a potential customer what they're getting for their money in such a short document. With books, we provide a table of contents and sample chapters. The T of C with a whitepaper has to be much, much better, because it's really all that the potential cusotmer has. Thus, a heading like "the next step" while OK for a book isn't as useful as "step 3 - error trapping" in communicating what the paper covers.

Read through the table of contents for whitepapers that are already available on our Web site. (Click on Catalogs, then Whitepapers, then drill down to the Table of Contents link for a specific whitepaper.)

I urge you to read through the T of C first, to see how well (or poorly) it communicates what is is supposed to be covered in the whitepaper itself. Does it make you WANT to spend the few bucks for the paper itself? Then read through the paper itself, and see if its contents have been accurately conveyed - do you STILL feel you got your moneys worth? (Presumably, if you didn't feel it was worth the money at the beginning, you wouldn't have bought it.)

How to go about submitting a whitepaper proposal

Since whitepapers don't get sold through all of the traditional avenues that printed books are, there isn't as formal a process for submitting a proposal. Simply sending me an email with the following items is good enough:

Proposed author(s)
Proposed tech editor (if you have one)
Estimated # of pages
Estimated start and finish dates
A one paragraph (100 - 250 words) abstract
A main level outline, at least one item per two pages of paper
List three things the reader will learn from your whitepaper

Of course, feel free to include anything else of interest!

How to go about writing a whitepaper

A whitepaper is just like a chapter (or two) in a book of course. So you'll just use the template from the HWP Author Kit (see the link to the left). You'll probably want to pass a draft by me before submitting a final copy. You'll also have to submit the Table of Contents in a text file - all of the headings in the whitepaper - each level suitably differentiated.

Once I receive your whitepaper, I'll have it copy edited and laid out, and sent back to you for final review. Once you approve, we'll finish it up, post it, sell the living daylights out of it, and make mee-llions and mee-llions <evil cackle>.

Back to Top

Help  |   Contact Us  |   Legal  |   Privacy  |   Copyright  |   Join Our Mailing List