Re: Documenting two similar interfaces

Subject: Re: Documenting two similar interfaces
From: Bill Swallow <techcommdood -at- gmail -dot- com>
To: Sarah Blake <Sarah -dot- Blake -at- microfocus -dot- com>
Date: Tue, 23 Jun 2009 11:24:49 -0400

Sit the project manager, product manager, and other project leads down
and bring this up. Ask which will be the default UI, not just when
installed, but how it will be marketed and pitched. If they want both
documented, find out if they want them in the same Help file or as two
different Help files (in which case it's up to the dev folks to point
to the right one from the right skin). As for authoring, I would push
for two different help files and single-source the content,
conditioning for classic and ribbon.

On Tue, Jun 23, 2009 at 11:15 AM, Sarah Blake<Sarah -dot- Blake -at- microfocus -dot- com> wrote:
> To save me reinventing the wheel...
> I'm currently working on a project where we're upgrading the UI to use a
> new 'ribbon'-style interface (a la MS Word), but users will also have
> the option to use the familiar 'classic' interface.  The documentation
> will therefore need to deal with both.
> I'm not sure which of these will be the default; I suspect the ribbon
> interface, but I don't know for certain.  And while the placement of
> functions within menus is similar between the two, it's not identical.
> At the moment, I'm looking at basically doing the following:
> 1. From Furniture > Hatstand (or Interior > Furniture > Hatstand if
> using the Classic interface)
> ...but the help is the approximate size of War and Peace, and giving
> double directions for each task seems a bit cumbersome, especially when
> (as seems inevitable) I'm going to have to go back through in a couple
> of releases' time, removing one set.
> If I have to, then I have to, but does anyone else who's gone through
> this process have any tips or suggestions?  (The documentation format is
> CHM, created from XML source files.)

Bill Swallow

Twitter: @techcommdood

Available for contract and full time opportunities.

Free Software Documentation Project Web Cast: Covers developing Table of
Contents, Context IDs, and Index, as well as Doc-To-Help
2009 tips, tricks, and best practices.

Help & Manual 5: The complete help authoring tool for individual
authors and teams. Professional power, intuitive interface. Write
once, publish to 8 formats. Multi-user authoring and version control!

You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-

To unsubscribe send a blank email to
techwr-l-unsubscribe -at- lists -dot- techwr-l -dot- com
or visit

To subscribe, send a blank email to techwr-l-join -at- lists -dot- techwr-l -dot- com

Send administrative questions to admin -at- techwr-l -dot- com -dot- Visit for more resources and info.

Please move off-topic discussions to the Chat list, at:

WinHelp -- the platform that wouldn't die: From: Dan Goldstein
Documenting two similar interfaces: From: Sarah Blake

Previous by Author: Re: The Tech Writer as Smuggler
Next by Author: Re: Documenting two similar interfaces
Previous by Thread: Documenting two similar interfaces
Next by Thread: Re: Documenting two similar interfaces

What this post helpful? Share it with friends and colleagues:

Sponsored Ads