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.
Re: Teaching a practical business writing class and looking for professional rubrics
Subject:Re: Teaching a practical business writing class and looking for professional rubrics From:voxwoman <voxwoman -at- gmail -dot- com> To:Keith Hood <klhra -at- yahoo -dot- com> Date:Tue, 18 Aug 2009 13:00:18 -0400
On Tue, Aug 18, 2009 at 10:32 AM, Keith Hood <klhra -at- yahoo -dot- com> wrote:
> Yes, obviously our output has to please the boss and do what he wants it to
> do. But on the other hand...
>
> I can't speak for anyone else on the board, but I contend that "creativity"
> is not a bad thing; at least, not when done right. When I have used that
> word in previous arguments this board has seen on this point, I meant
> finding ways to write things, to lay out pages, so that the end result was
> not full of tedious repetition that annoyed the reader.
>
> One of the most commonly heard complaints about tech docs is, they are hard
> to read because they are so boring. Many have content that is so repetitive
> it is mind-numbing. Too many are full of pages that look exactly the same
> except for the difference of a few words. They keep using the *exact* same
> phrases over and over until the reader is sick of seeing them. You can
> actually make documents painful to read with excessive consistency.
>
A case-in-point is the book *HTML, XHTML and CSS (Visual Quick-Start Guide),
*by Rob Huddleston uses the exact wording for every CSS command, and in
about 5 cases, didn't bother to update the text from the previous command,
so that the text didn't even apply to the section. It was very disappointing
to see that in an expensive published book.
Free Software Documentation Project Web Cast: Covers developing Table of
Contents, Context IDs, and Index, as well as Doc-To-Help
2009 tips, tricks, and best practices. http://www.doctohelp.com/SuperPages/Webcasts/
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-