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.
My first thought was one that may or may not address your situation. If
you're working with Robohelp, you might be able to tag your files in such a
way that you can compile versions that vary by presentation type. I do this
with one of my help systems to compile versions by customization type. It
allows me to send a version of the help system that varies by the specific
functionality a client has purchased. A lot would depend on if the steps
would change based on the type of device it's being presented on.
Sounds like a job for single sourcing!
Regards
Connie P. Giordano
Senior Technical Writer
Advisor Technology Services
A Fidelity Investments Company
704-330-2069 (w)
704-330-2350 (f)
704-957-8450 (c)
connie -dot- giordano -at- fmr -dot- com
"Pray that there's intelligent life somewhere up in space, 'cause I'm afraid
that we've been cheated here on Earth" - Clint Black "Galaxy Song"
-----Original Message-----
From: Jim Shaeffer [mailto:jims -at- spsi -dot- com]
Sent: Tuesday, September 30, 2003 9:53 AM
To: TECHWR-L
Subject: Step-by-step instructions for a variable GUI?
How do you document step-by-step instructions for an ever-changing GUI?
The horns of the dilemma:
Horn 1: We are moving our software products to a "3-tier architecture". Tier
1 is data, tier 2 is the executables, tier 3 is the presentation layer. The
strategy is that the independent presentation layer will allow our software
to run anywhere and everywhere (desktops, laptops, tablet PCs, hand helds,
PDAs, cell phones and devices that haven't been invented yet).
Horn 2: Our users need detailed, step-by-step instructions for every task
they can perform while using our software. They complain that we don't give
them enough step-by-step procedures, and they have amply demonstrated their
need for them over the years. Further, it is obvious that there is no such
thing as too much hand holding or too great a level of detail.
Horn 3: Our user documentation is in the form of context sensitive Help
files. Traditionally, Help files are tied to executables. Our plan, is that
the executables will remain constant while the GUI (presentation tier)
adapts itself to any and every delivery device.
Horn 4: The strategy of the independent presentation layer is part of our
plan to get our software to be installed and used by people who are even
less technical than our current user population.
I'm looking for both conceptual and technical advice. None of this stuff is
due yesterday, so this is a planning issue, not an emergency.
Thanks in advance,
Jim Shaeffer (jims -at- spsi -dot- com)
NEED TO PUBLISH YOUR FRAMEMAKER CONTENT ONLINE?
?Mustang? (code name) is a NEW online publishing tool for FrameMaker that
lets you easily single-source content to Web, intranets, and online Help.
The interface is designed for FrameMaker users, so there is little or no
learning curve and no macro language required! See a live demo that
will take your breath away: http://www.ehelp.com/techwr-l3
---
You are currently subscribed to techwr-l as:
archive -at- raycomm -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- raycomm -dot- com
Send administrative questions to ejray -at- raycomm -dot- com -dot- Visit http://www.raycomm.com/techwhirl/ for more resources and info.
