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.
> Hello all,
> We are putting up a quarterly newsletter for our technical
> audience and
> I know companies have blogs on their sites, usually for marketing
> purposes. I'd like to hear your opinions about replacing the
> with a technical blog (considered a more updated form of
> Any thoughts will be greatly appreciated.
> One caution under the "always know your users" clause... before you
> decide to go "blog", you might want to confirm that the
> majority of your
> users can actually access blogs. Some workplaces (like my
> own, up until
> very recently) had very tight IT policies that restricted
> anything with
> the word "blog" in the URL. Didn't matter if it was as much of a time
> waster as Stuff On My Car or something really useful like a Microsoft
> Developer's blog or blogs on the Adobe site. All blocked. And the
> fight with IT to get access for a specific site could take months. It
> wasn't worth it.
> I personally have nothing against blogs. I read them. I have my own
> (not tech writing related). But it can be helpful to know some
> workplaces have a blanket bias against all of them, useful or not.
> Might want to touch base with your users to make sure they
> can actually
> *get* to it, or go with the general design and concept of a blog but
> just stay away from the "b" word.
Do what some technical bloggers and many money sites do: Both.
Blog frequently on small, self-contained (where possible) topics, or
serialize big topics (when possible) then publish the blogs as-or-in a
weekly/monthly/quarterly newsletter. The major hosting sites and the
blogging software have that as an option (automatic or semi-automatic*),
(* Automatic version would just gather what you'd blogged in the
interval since the last compilation, slap a canned header and ToC on it,
and send it out as mail to your e-mail opted-in subscribers.
Semi-automatic version does the same thing, but pauses to let you
tweak/edit or add additional value-content before hitting [Send] - like
some helpful comments that your individual blog items might have drawn
from reader feedback, or your "clarification" after too many readers
reported being confused or insufficiently informed by this-or-that
blog... it happens...)
Anybody who wants just the blogs can opt out of the newsletter. Anybody
who wants just the newsletter can just not bother to go read your blogs.
Given that your content is valuable, many people will want both - to see
it as it's written, and also to receive it as a handy "archive"
delivered to their inbox at a later time. Also, it's the perfect
solution for clients living with draconian browsing restrictions.
The information contained in this electronic mail transmission
may be privileged and confidential, and therefore, protected
from disclosure. If you have received this communication in
error, please notify us immediately by replying to this
message and deleting it from your computer without copying
or disclosing it.
ComponentOne Doc-To-Help 2009 is your all-in-one authoring and publishing
solution. Author in Doc-To-Help's XML-based editor, Microsoft Word or
HTML and publish to the Web, Help systems or printed manuals. http://www.doctohelp.com
Help & Manual 5: The complete help authoring tool for individual
authors and teams. Professional power, intuitive interface. Write
once, publish to 8 formats. Multi-user authoring and version control! http://www.helpandmanual.com/
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-