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.
To what extent is it your decision as the tech
writer/tech writing department how to lay out manuals,
and to what extent is it the programmers' decision?
>>> currently, our writers decide the style of manuals, but work with
programmers to understand how they need information.
A programmer who
usually does not need documentation recently needed a
doc done and complained that he wants it without the
side-head - in other words, he wants the lines to go
all the way across. (He didn't say why.)
>>> The programmer's of our largest client (over 14000 pages and climbing)
used to decide their format. This was because they had very little
experience with good designers/writers. They had a multitude of experience
with bad designers/writers. It took us 2-3 years to convert the programmers
to buy into a style manual that we would control. Now everything is very
nice, but we did make some small concessions to the client. The concessions
were worth it in good will.
My feeling is that, I don't tell them how to program;
they don't tell me how to lay out documents. But I am
willing to listen to *your* feedback. (Since you are
fellow tech writers.)
>>> this sounds like a war in the making if you ever voice your opinion. I
occasionally do tell the programmer's about bugs I find and GUI issues that
I find "awful," just as they find typos, misspelled words, and critique my
document design. I can take it and I find they can too.
If a programmer is really interested in doc design (enough to insist on a
design), he may have some insight... or not. But if he is really interested
you may be able to school him in the right direction.
Develop HTML-Based Help with Macromedia Dreamweaver 4 ($100 STC Discount)
**WEST COAST LOCATIONS** San Jose (Mar 1-2), San Francisco (Apr 16-17) http://www.weisner.com/training/dreamweaver_help.htm or 800-646-9989.
Sponsored by ForeFront, Inc., maker of ForeHelp Help authoring tools
for print, WinHelp, HTML Help, JavaHelp, and cross-platform InterHelp
See www.forehelp.com for more information and free evaluation downloads
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.