TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
Techwhirl Technical Communication Recap for July 20, 2012
Subject:Techwhirl Technical Communication Recap for July 20, 2012 From:TechWhirl Admin <admin -at- techwhirl -dot- com> To:Techwr-l <techwr-l -at- lists -dot- techwr-l -dot- com> Date:Fri, 20 Jul 2012 11:09:42 -0400
*This week’s update on technical communication and the TechWhirl community
is supported by Platinum sponsor ComponentOne & their Doc-To-Help Help
Authoring Tool <http://goo.gl/QcMWA> | http://bit.ly/doc-to-help*
This was a week of varied, but relevant and lively discussions on the
TechWhirl email discussion
list<http://www.techwr-l.com/about-technical-writing-discussion-groups.html>,
the kind of week that shows the broad range of the technical communication
field. Section 508 compliance, strategies for organizing help systems,
handling production of multi-language documents, tool questions and
answers, trends and careers…all of which meant we had conversations with
newbies and veterans, in all sorts of industries.
TechWhirl’s customers are technical communicators, and our community on the
email list is just one way that we stay in touch with our customers. We
also send and receive emails, exchange tweets, post to FaceBook, LinkedIn
and Google+ <https://plus.google.com/b/103754021966257477744/>, announce
jobs <http://jobs.techwhirl.com/>, release news <http://news.techwhirl.com/>,
and deliver topical content that—happily—our customers are more than
willing to respond to. As technical communicators roles in our
organizations’ customer service or customer experience strategies should
take into account all the various ways those customers want and do interact
with us. Technical communication isn’t just about creating good technical
content (after all, we could come up with thousands of interpretations as
to what constitutes “good.”). It’s about understanding the customer, what
they want, how our companies are delivering it, and aligning the content
with those expectations and needs.
- Tech Writer This Week for July 19, by Craig Cardimon | http://bit.ly/LYRBtc
- Classic Technical Communication Humor: Software Supreme, by K. John
Russell | http://bit.ly/LXn9Q8
- Technical Communication Poll: Those Pesky People Skills | http://bit.ly/LWgC85
- Unified Content That Serves the Customer: Let’s Come Out of the Dark
Ages, by Jacquie Samuels| http://bit.ly/NcCmwn
- Our Google Plus Page – what’s happening behind the scenes | http://goo.gl/SO0R4
- Will you be our Friend? Please, you know you want to click | http://goo.gl/tDrW7
- Want all this TechWhirl goodness a few characters @ a time | http://goo.gl/itjDg
- Updates from TechWhirl delivered to your email in box | http://bit.ly/tjshxU
- Or, try our RSS feed (great on Flipboard) | http://goo.gl/msLzu
SPONSOR-Luv
We want to send a very special “thank you” to our sponsors for their
support.
TechWhirl.com
Online Magazine and Discussions for Today's Tech Writer
Follow TechWhirl on
Twitter: @TechWriterToday
Facebook: facebook.com/techwriterlist
Google+: plus.ly/TechWhirl
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Create and publish documentation through multiple channels with Doc-To-Help. Choose your authoring formats and get any output you may need.
Try Doc-To-Help, now with MS SharePoint integration, free for 30-days.