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:Two interfaces, one product From:scott -at- soffront -dot- com To:techwr-l Date:Tue, 2 May 2000 11:29:19 -0700
Hi,
I need some recommendations. I am writing paper documentation for a product
that has two different interfaces: one standard, the other through a Web
browswer (Internet Explorer or Netscape Communicator).
The basic functionality is shared between the interfaces, but the screens
are drastically different. In addition, some buttons are also inconsistent.
I just finished a 50 page first draft, but completely neglected the second
interface. I'm trying to decided whether to start a new guide just for the
second interface, or somehow intertwine the second interface into the
first. Did I mention I used many screen shots? I could easily double the
guide to 100 pages (because the procedures a just a bit different).
Has anyone else faced a similiar situation? I'd love to see some examples.
Please respond via e-mail:
scott -at- soffront -dot- com
