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.
Subject:How long to create a help screen? From:Arthur Comings <atc -at- CORTE-MADERA -dot- GEOQUEST -dot- SLB -dot- COM> Date:Wed, 24 May 1995 11:05:32 PDT
I sent this message a couple of days ago with a subject line that
wasn't really descriptive. Perhaps that's the reason I received no
replies. Maybe our server had a discreet crash; maybe I've been
blackballed.
At any rate, I offer the question again with my apologies and a more
appropriate subject line.
How do you estimate time that you'll spend creating hypertexted Help
screens -- when the information itself is already at hand?
Seems to me that a day per screen, fully hypertexed and debugged, is not
unreasonable, but I can imagine a prospective employer blanching when
they found out how many screens a decent-sized program might need.
Come to think of it, I don't have much of an idea of that, either,
although I have taken a workshop on the subject that covered scoping,
etc.
I'm using FrameMaker's hypertext tools. I sure do like the way I can
macro-ize the process.
I'll summarize answers to the list, unless it looks like most
respondees are copying the list anyway.
