A Community for all of us! 
Writer's Guidelines
What?
How-tos with a slice of lime. Overviews with pizzaz. Distilled wisdom with verve. In short, we're looking for punchy, positive articles about technical writing that hook and keep a reader. Think of a tree-fort with the words on a makeshift sign reading, "Dry, boring, and dull not allowed!" We are seeking unique voices that reflect the worldwide reach of tech comm.
Audience: Our audience is technical communicators, from every type of industry, skill level, and tool preference. Articles about grammar, Framemaker, Acrobat, managing tech comm groups, cross-cultural communication -- if it flows out of your experiences as a technical communicator, it's good for an article.
Length: Articles should be 500-3000 words; we're looking to keep it within 1-4 pages of HTML.
Grammar/Structure: Make sure that the article has been properly spellchecked, and that it possesses a strong opening, a satisfying conclusion, and logical development of its main points in the spaces between. If the article does not have those features, it will be rejected.
Format: Articles should be in either Word Doc format, RTF, or plain text.
Payment: We offer payment at this time, at a flat rate of $50. We'll pay more as we grow, and we won't forget the stalwart souls who submitted our first articles. Promise.
Where?
Send all submissions to editor at techcommpros.com.
How?
Articles almost always go through a multi-step review process. If the article is deemed worthy, then it will be edited. If the article needs edits that require detailed knowledge of the subject matter, then the article may be sent back for clarification. This may happen a maximum of three times. Once the edits are made, you'll get a galley which will allow you to see the article in HTML before it is published. If you have any last minute changes, suggest them then. We'll take them into account, but we may or may not make them. Then, the article is published. Voila`!
Next?
If you have any questions, feel free to drop the editor a line and ask. We're looking forward to your submissions and the growth of TCP.
