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.
> -----Original Message-----
> From: On Behalf Of mlist -at- safenet-inc -dot- com
[...]
> >However, since the commands or sub-commands that any one role can see
> >are exactly the same as those commands when seen and used by a higher
> >role, I want to re-use the same help topics/pages where possible.
>
> >Rather than try to work out some scheme where each role gets a
> >physically different WebHelp, I'd like them all to use the same help,
> >but I'd provide page-top icons or section-highlighting icons
> >to let them
> >know if a page applies to their role. If it's just informative stuff
> >(Concepts) I'd leave out the icons. But for anything operational,
> >there'd be one, two or three icons at the top of the page,
> >symbolizing
> >who should bother reading.
>
> >Suggestions? Opinions that it's a bad idea in general (give reasons)?
> I can understand why you want to do this (it's easier), but
> why is this better for your users?
Well... I can see your point if I was trying to cut corners on
a requirement...
But, this is purely my idea for added value, so that users
can see immediately, without reading further, that a command
is not for them. Some customers won't bother with the separation
of roles (they'll just have one person being "admin", and to
heck with those lesser roles). Others may have the same people
logging in as one or another role, just to avoid the clutter
of extra commands, or for company procedural reasons,
or they may be writing scripts for one reason or another.
In some cases, a PC would have a session open to the appliance,
always logged in as monitor, but when necessary, an "operator"
or "admin" could log in to fix/maintain some aspect of the
system. Having the visual flag in the help might remind
them to be sure to log out, leaving only "monitor" capability
on that connection.
The CLI has some sparse syntax "help", but my WebHelp expands
on it and provides examples and links to other Help, etc.
As I said, the interface to the product is command-line, so
it's not like I can determine the role they have logged in
and present selective help. Perhaps when we move into the
twentieth century and incorporate a GUI... :-).
Kevin
The information contained in this electronic mail transmission may be privileged and confidential, and therefore, protected from disclosure. If you have received this communication in error, please notify us immediately by replying to this message and deleting it from your computer without copying or disclosing it.
Now Shipping -- WebWorks ePublisher Pro for Word! Easily create online
Help. And online anything else. Redesigned interface with a new
project-based workflow. Try it today! http://www.webworks.com/techwr-l
Doc-To-Help 2005 now has RoboHelp Converter and HTML Source: Author
content and configure Help in MS Word or any HTML editor. No
proprietary editor! *August release. http://www.componentone.com/TECHWRL/DocToHelp2005
---
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 http://www.techwr-l.com/techwhirl/ for more resources and info.
