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: Subject: Re: New doc group: FrameMaker or Flare?
Subject:Re: Subject: Re: New doc group: FrameMaker or Flare? From:"Gene Kim-Eng" <techwr -at- genek -dot- com> To:<techwr-l -at- lists -dot- techwr-l -dot- com> Date:Wed, 5 Jan 2011 08:54:24 -0800
If the situation is likely to turn out to be one in which the developers are
going to revise existing docs and possibly even create new ones with contract
writers being brought in "as needed" (IOW, when the developers bollux up the
drafts so badly that nobody in-house can fix them), then my advice would be to
develop simple templates in the existing WP infrastructure, find one person in
the company who is interested in learning how to tag styles and generate
deliverable PDFs (perhaps an admin or doc control specialist with an interest),
then encourage the developers to type their input into the WP or WordPad as
unformatted text and pass it to that person for formatting and final production
(and the company to give that person a raise to go with the added
responsibility). A single point operation in this area will help avoid a lot of
chaos in the documentation.
Gene Kim-Eng
----- Original Message -----
From: "Bill Swallow" <techcommdood -at- gmail -dot- com>
> I'd caught that after posting in this thread (one of the pitfalls of
> changing the subject line mid-stream on a listserv). And you're right,
> idiots are ingenious (see my hammer/screwdriver/wrench examples in my
> reply to the other thread). So part of the solution is to pick a
> self-contained tool to minimize effort in setting up an authoring
> environment. Another part is developing - and documenting - a solid
> yet minimalist template and style guide. The third is pre-exodus
> training. And the fourth is leaving your contact info behind for
> follow-up engagements.
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. http://www.doctohelp.com
---
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-