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 have a problem that I am hoping some of you seasoned veterans can help me
with.
I am writing a user's guide for an add-in application. Although both the
add-in application and the larger application are currently being developed
by my company, the larger application's user's guide is being written by
another company. I have the rough outline for the larger application's
user's guide, but I cannot wait for them to finish writing their manual
before starting mine. The add-in application is actually quite a large
application in its own right and duplicates a lot of the larger
application's menus, toolbars, dialog boxes, interface, etc.
My original idea for writing this user's guide was focusing on the add-in
application's extensions and referring users to the other manual to perform
the majority of the functions. For example, "Creating a Project" is
something you can do using both applications. However, this will result in
far too many references to the other manual. Has anyone written this type of
manual before?
Any help would be greatly appreciated.
Dal
dal_gemmell -at- email -dot- syscom -dot- com -dot- tw
