Pages

Showing posts with label writer. Show all posts
Showing posts with label writer. Show all posts

Monday, October 10, 2011

Another Way for Writers to Earn Money: Whitepapers

Writers can do so many things: We can write fiction and nonfiction books. We can teach others how to write. We can be editors or marketing writers. We can be instructional designers or technical writers.  Here's another opportunity for those of us who know how and love to write:  Writing Whitepapers.



The bog Klariti: Small Business Tips for Smart People outlines what you need to know to get started:

"If you’ve got good writing skills and have in-depth subject matter expertise, you should be able to generate additional income by writing white papers.
I started writing them by accident when the in-house white paper writer fell ill and someone had to write it. Looking back, it wasn’t the greatest document I’ve written but the client accepted it and the customer response was positive.
Since then, I’ve managed to carve out a niche as a white paper writer, which has been very helpful when other avenues dried up. I thought I’d share a few tips on how I got started, how to build up a client list, and how much you should charge."

Click here to read tips on writing White Papers:

Friday, June 24, 2011

4 Golden Rules of Capitalization in Technical Documents

We all need an occasional refresher . . . .  from Technical Writing Tips, Tools & Templates





It is ebay or eBay or Ebay? How Technical Writers use capitalization in user guides creates many problems for editors, reviewers, and users. Part of the problem is a lack of guidelines and style guides. What you think looks fine break some style guide rule you were unaware of.

The Capitalization of Microsoft

A good example is the word Microsoft. When it started out, it was MicroSoft. Then it changed the uppercase S to a lowercase.
So, what do you do with all the legacy documents or international materials, for example, business documents for Chinese readers?

Guidelines for Capitalization

The Golden Rules of Capitalization in Technical DocumentsIn general, use capitalization rules whenever possible – for example, common nouns are usually all lowercase and proper nouns are always capitalized.
  1. Never use all uppercase letters for emphasis.
  2. Follow the capitalization rules of software as necessary, as in case-sensitive keywords.
  3. Do not capitalize the spelled-out form of an acronym unless specified otherwise in the List of Acronyms and Abbreviations.
  4. Avoid over-capitalization.
Capitalization Of User Interfaces Elements
Microsoft recommends the following capitalization rules for interface elements:
  • Menu names, command and command button names, and dialog box titles and tab names: Follow the interface. Usually, these items use title caps. If the interface is inconsistent, use title caps.
  • Dialog box elements: Follow the interface. Newer style calls for these items to use sentence caps. If the interface is inconsistent, use sentence caps.
  • Functional elements: Capitalize the names of functional elements that do not have a label in the interface, such as toolbars (the Standard toolbar) and toolbar buttons (theInsert Table button).
  • Do not capitalize interface elements used generically, such as toolbar, menu, scroll bar, and icon.
  • The Golden Rules of Capitalization in Technical Documents Do not capitalize unless it is case-sensitive.

Looking for examples

One of the hazards of having a love of words is that you see things that others take for granted.
So, when it comes to caps or should that be capitalizations… I see these everywhere.
For example:
Is it web site or Web Site or Website?
Is it the Bible of The Bible?
Is it IBM or I.B.M.?
What other examples would you add?