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: Mayvbe O/T? - Text development vs tech writing
Subject:Re: Mayvbe O/T? - Text development vs tech writing From:"Dana Worley" <dana -at- campbellsci -dot- com> To:"TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com> Date:Fri, 8 Jun 2001 08:51:07 -0600
Judy Ferril asked:
> Is anyone out there just developing text for user's manuals without
> regard to format, design, graphic choices, etc.?
>
> I am curious how this works as I have been asked to do so and am
> finding it difficult. Just write text and turn it over to a formatter
> (?). This person then chooses graphics, set up, etc. and applies it to
> the text. I usually tie all of these together to make it flow, not to
> mention instructional. Any suggestions for removing my mental block
> would be appreciated.
When I author help files (which is the majority of my writing tasks),
I am the one who decides the "look and feel" of the end product.
However, when I author manuals, I just write the manual and do not
worry about the final format. Once the manual is very close to a
final draft, I hand it over to someone else who is responsible for
formatting all our manuals to make sure they have a consistent
style. I prepare my documents in Word (gasp!) and make sure that
I use consistent styles for headers, paragraphs, etc. This makes it
easier on the person who will put it into the final format.
I do, however, provide all screen shots. If you don't provide the
actual screenshots, you should at least be the one that dictates
which screen shots appear in the manual. You are the one writing
the text -- you know what message you are trying to get across,
and what screen shots and illustrations will help to convey that
message. (Also, in my case, the person who formats the
document is truly just a "formatter" and can't really handle anything
else...). If an illustration needs to be done, we have someone else
in-house who does that (I'm not an illustrator -- I am a writer).
My company wants all its documents formatted the same. I may
not like the format they have chosen, but this is just one of those
areas where I have to "let go" and not worry about it. And, in the
end, it IS just one less thing I have to worry about.
*** Deva(tm) Tools for Dreamweaver and Deva(tm) Search ***
Build Contents, Indexes, and Search for Web Sites and Help Systems
Available now at http://www.devahelp.com or info -at- devahelp -dot- com
Sponsored by Cub Lea, specialist in low-cost outsourced development
and documentation. Overload and time-sensitive jobs at exceptional
rates. Unique free gifts for all visitors to http://www.cublea.com
---
You are currently subscribed to techwr-l as: archive -at- raycomm -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- raycomm -dot- com
Send administrative questions to ejray -at- raycomm -dot- com -dot- Visit http://www.raycomm.com/techwhirl/ for more resources and info.