We welcome all articles about technical communication and our community for our monthly newsletter. Our newsletter goes out to over 800 technical communicators in the GTA. It's great way to enhance your online presence, and get your name known among key decision makers. General article guidelines - the article must involve technical communication or any of its related areas including: product development and testing, training, e-learning, usability, and so on
- articles should be between 300 to 1,000 words long; 500 words is a good suggested length
- strive to make your article interesting and relevant; where possible, give examples of what you are trying to say
The newsletter is published the first day each month except during June, July and August, when it is not published. All articles must be submitted no later than one week before the first day of the following month. Topic ideas
- reporting on meetings and events
- interviewing speakers
- software reviews
- conference or seminar reviews
- book reviews (software tools, style guides, documentation processes, anything to do with technical
communication)
- tools, tips, and tricks
- courses or programs you are enrolled in
- adventures in technical communication
- your experience in the current job market
- current trends in technical communication
- how you solved a particular technical communication problem
- successful job-hunting strategies
- the "zen" of technical writing
- the value of technical communication to your company or clients
- new technology or research
- why you are a technical communicator, or about to become one
- what you like (and don't like) about technical communication
Please contact our newsletter editor with your ideas or if you have any questions. |
|
