資源s - 令状/Edit for Hentzenwerke

Wanna 令状 or edit a 調書をとる／予約する? Here's all you need to know about how the publishing 過程 作品 here.

• About HWP
• The Publishing 商売／仕事
• The 過程 at HWP
• 提案するing a 調書をとる／予約する
• The 契約
• Getting Paid
• Doing the 令状ing and Editing
• Source Code
• Ebook Stuff
• Our Covers
• Going to 圧力（をかける）
• Marketing
• 令状ing Whitepapers
• So You Want to be an Author
• So You Want to be a Tech Editor
• The HWP Author 道具

A 商業の whitepaper has a few せいにするs that 異なる from other types of 構成要素 we've produced in the past (i.e. printed 調書をとる／予約するs). This page explains what those せいにするs are so you know what you're getting into and what to do to 令状 a whitepaper for us.

What is a whitepaper?

I assume that you've already read about whitepapers under the Catalogs link on this 場所／位置. To come at it from the point of 見解（をとる） of an author, a whitepaper is your chance to discuss something that is 価値のある, but just not long enough for a 調書をとる／予約する by itself. 一般に, a whitepaper covers a 辛うじて 焦点（を合わせる）d 支配する, anywhere from 20 to 100 pages. It may or may not come with source code.

The （米）棚上げする／（英）提議する of contents

The 重要な 面 of a whitepaper is that it's difficult to explain 正確に／まさに to a 可能性のある 顧客 what they're getting for their money in such a short 文書. With 調書をとる／予約するs, we 供給する a （米）棚上げする／（英）提議する of contents and 見本 一時期／支部s. The T of C with a whitepaper has to be much, much better, because it's really all that the 可能性のある cusotmer has. Thus, a 長，率いるing like "the next step" while 承認する for a 調書をとる／予約する isn't as useful as "step 3 - error trapping" in communicating what the paper covers.

Read through the （米）棚上げする／（英）提議する of contents for whitepapers that are already 利用できる on our Web 場所／位置. (Click on Catalogs, then Whitepapers, then 演習 負かす／撃墜する to the （米）棚上げする／（英）提議する of Contents link for a 明確な／細部 whitepaper.)

I 勧める you to read through the T of C first, to see how 井戸／弁護士席 (or 貧しく) 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 正確に 伝えるd - do you STILL feel you got your moneys 価値（がある）? (推定では, if you didn't feel it was 価値（がある） the money at the beginning, you wouldn't have bought it.)

How to go about submitting a whitepaper 提案

Since whitepapers don't get sold through all of the 伝統的な avenues that printed 調書をとる／予約するs are, there isn't as formal a 過程 for submitting a 提案. 簡単に sending me an email with the に引き続いて items is good enough:

肩書を与える
提案するd author(s)
提案するd tech editor (if you have one)
概算の # of pages
概算の start and finish dates
A one paragraph (100 - 250 words) abstract
A main level 輪郭（を描く）, at least one item per two pages of paper
名簿（に載せる）／表（にあげる） three things the reader will learn from your whitepaper

Of course, feel 解放する／自由な to 含む anything else of 利益／興味!

How to go about 令状ing a whitepaper

A whitepaper is just like a 一時期／支部 (or two) in a 調書をとる／予約する of course. So you'll just use the template from the HWP Author 道具 (see the link to the left). You'll probably want to pass a 草案 by me before submitting a final copy. You'll also have to 服従させる／提出する the （米）棚上げする／（英）提議する of Contents in a text とじ込み／提出する - all of the headings in the whitepaper - each level 都合よく differentiated.

Once I receive your whitepaper, I'll have it copy edited and laid out, and sent 支援する to you for final review. Once you 認可する, we'll finish it up, 地位，任命する it, sell the living daylights out of it, and make mee-llions and mee-llions <evil cackle>.