Implementing a glossary

Subject: Implementing a glossary
From: Neal Moogk-Soulis <neal_ca -at- rocketmail -dot- com>
To: "TECHWR-L" <techwr-l -at- lists -dot- techwr-l -dot- com>
Date: Tue, 1 Nov 2005 14:12:15 -0800 (PST)


I'm currently compiling a glossary to accompany
our next software release. Once we have the
content gathered, I need to figure out how to get
this information out to the user. I'm using
FrameMaker and Robohelp. Here are the

1. There is no user guide. Most users (85 to 90
per cent) will be accessing the product online.
Their only source of information is an online
help system.

2. There is a feature guide and a dev guide. This
document is distributed as a PDF so a glossary
chapter is feasible. However, these docs are
generally not read in paper form so the
possibility exists to exploit PDF features.

3. The content is context sensitive. Terms
(usually UI fields) have different meanings,
definitions or levels of permission depending on
where the user is in the UI or what permissions
the user has. For the online user, I'm thinking
that a Glossary in the Help TOC might be the best

4. Project size. There are over 400 separate help
pages (one per UI page) with over 300 terms which
may appear multiple times either in the same page
or across several pages. We already have some
difficulty maintaining order across the project
and I don't want to add another level (ie pop-up
links on individual words) that would be too hard
to maintain.

I'm curious to see how other people have provided
glossary definitions to online users. The two
options that I can think of are either a separate
glossary page or pop-ups when you roll over a
word. The former solution seems to be the quick
and dirty way and the latter solution seems to
mean a lot of work, especially if you want to
catch each word, but potentially more useful to
the user. Are there other options out there?



Yahoo! FareChase: Search multiple travel sites in one click.


Try WebWorks ePublisher Pro for Word today! Smooth migration of legacy
RoboHelp content into your new Help systems. EContent Magazine Decision-
maker review (October 2005) is here:

Doc-To-Help 2005 converts RoboHelp files with one click. Author with Word or any HTML editor. Visit our site to see a conversion demo movie and learn more.

You are currently subscribed to techwr-l as:
archiver -at- techwr-l -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- techwr-l -dot- com
Send administrative questions to lisa -at- techwr-l -dot- com -dot- Visit for more resources and info.

Previous by Author: Re: Career path in the third and fourth decades?
Next by Author: Ideas for Best Practices Image
Previous by Thread: Re: Can custom colors be saved in Word 2003?
Next by Thread: re: Implementing a glossary

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

Sponsored Ads