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.
I think you've received a number of excellent
responses. The few I'd focus on if I were you:
1. Set the record straight. There's no way in Hell
you'll get this done by Thursday that will be good
enough to satisfy the purpose. Though you did mention
that this is a prototype, your help system will
directly contribute to the usability of the product.
If the prototype is to be tested in mock simulations
(as I'm sure it will), poor documentation/help is not
going to help the prototype along. You need to express
that the source document was created haphazardly with
no regard for uniformity in design or future
enhancement. Basically, you're trying to reconstitute
fruit from a smoothie.
2. Spend time stylizing the manual. Or, have someone
do it for you while you lay out the groundwork for the
Help.
3. Spend time learning about HTML Help. Visit Web
sites, buy books and ask questions here and at
winhlp-l.
4. Keep the resume polished. Not "just in case", but
for your own benefit. If you can't get #1-#3 to work
for you, this #4 is your best ticket to a better
situation.
Good luck!
=====
Bill Swallow
Technical Writer
PowerAdz.com
518.687.6107
bswallow -at- poweradz -dot- com
__________________________________________________
Do You Yahoo!?
Get Yahoo! Mail ? Free email you can access from anywhere! http://mail.yahoo.com/
