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.
However, there are some tasks that seem basic that require some
For example, I have an intranet page that is divided into three frames.
One frame is the main menu, another is a local menu that depends on the
main menu selection, and the third holds the content. When the reader
clicks a main menu item, a new local menu appears, and new content
appears. It turns out that there is no simple way to show new content in
more than one frame on a single click event. I could have displayed a
whole new frame set, but that would have been slow and would have looked
awkward - the whole browser window would have been updated.
So, instead, I asked one of our web guys, who loaned me a copy of
programmer) to having the page programmed took me about two hours. There
were examples in the book that got me most of the way there, but I did
have to modify them a bit beyond simply replacing page names, so I had
to learn the basics of the language.
It's not a particularly difficult language, and there are good books out
there. Whether a technical writer should learn to write it or hand it
off to a specialist depends on the situation. In my situation, I'm
expected to "get my hands dirty" so I learned some of the basics. I may
end up being the specialist in my group - I tend to wallow in silicon
more than the other writers here. In a company where people tend to
specialize more, or in a situation where the programming is more
complex, a specialist might be the way to go.
>From: Marcel Uljee[SMTP:m -dot- uljee -at- PECOMA -dot- NL]
>Sent: Tuesday, March 25, 1997 2:32 AM
>To: TECHWR-L -at- LISTSERV -dot- OKSTATE -dot- EDU
>More and more technical writers participate in the production of
>Webpages. That's why we are wondering if it is useful to learn to write
>or should they consult a specialist, like they consult a specialist who
>takes care of the graphics?