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.
Re: suggestions on how to "hide" UI-based topics in online Help TOC?
Subject:Re: suggestions on how to "hide" UI-based topics in online Help TOC? From:Sue McKinney <smckinn2001 -at- yahoo -dot- com> To:techwr-l -at- lists -dot- techwr-l -dot- com, Donna Barbieri <deebeema -at- yahoo -dot- com> Date:Mon, 24 Mar 2008 12:38:43 -0700 (PDT)
I agree with Bill Swallow's suggestion to leave the UI topics in as the context-sensitive anchor points for the Help. I would then just name them by the interface name, e.g., XYZ Page. I usually put "see also" links AND "related procedures" links at the bottom of interface help topics. As Bill said, multiple procedures may be able to be performed in the interface; this way all the users are covered. Then the procedure topics can be named very specifically, e.g., Add an ABC to the XYZ.
My TOCs have generally included all topics, sectioned as follows:
You can also put all the procedures in one section, unless there are too many. My system had multiple modules, so each module had intro, each interface and related, and a procedures "chapter" with an intro topic listing the procedures and all the procedures in alpha order. That way the users can look at the interface topics and see related procedures or go directly to the procedures.
Good luck!
Sue
Bill Swallow <techcommdood -at- gmail -dot- com> wrote:
I really had trouble following your post, but as a suggestion, leave
the UI specific topics in, leave them as the context-sensitive anchor
points for the Help, and build in procedural information to which you
link from the UI topics. This way if one UI screen can be used by
users for 5 purposes, they get to that one UI topic and from there can
choose in the help what they're doing for more targeted info.
On Mon, Mar 24, 2008 at 11:38 AM, Donna Barbieri wrote:
> Here is the situation - I am working as a contractor
> at a company that had a Tech Writing intern (who is
> related to someone in dev). This intern produced an
> entire WebHelp system for the application. However,
> the Help system is 100% UI specific. Topics such as
> "using XYZ" really include information about what is
> on a particular screen.
> I have been tasked with creating "usable" Help for
> first time users AND with keeping the existing Help
> for a release in the next two weeks.
>
> Since, apparently, this HAS to be there I'd like to
> minimize it's impact on users. I am thinking of
> introducing the task-based topics as one normally
> would and then renaming all the existing topics and
> including them in a logical hierarchy (oh, I didn't
> mention the current TOC has two levels - which could
> be bc there are no keywords and the index suxs - but I
> digress yet again...)...anyway, so I want to create a
> hierarchy so these topics aren't cluttering the TOC -
> question is - what should these "topics" be called I
> really want to steer away from "using XYZ Page" and
> was thinking "XYZ Options" "XYZ Page" "About XYZ"? Any
> suggestions?
--
Bill Swallow
HATT List Owner
WWP-Users List Owner
Senior Member STC, TechValley Chapter
STC Single-Sourcing SIG Manager http://techcommdood.blogspot.com
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Create HTML or Microsoft Word content and convert to Help file formats or
printed documentation. Features include support for Windows Vista & 2007
Microsoft Office, team authoring, plus more. http://www.DocToHelp.com/TechwrlList
True single source, conditional content, PDF export, modular help.
Help & Manual is the most powerful authoring tool for technical
documentation. Boost your productivity! http://www.helpandmanual.com
---
You are currently subscribed to TECHWR-L as smckinn2001 -at- yahoo -dot- com -dot-
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 http://www.techwr-l.com/ for more resources and info.
---------------------------------
Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Create HTML or Microsoft Word content and convert to Help file formats or
printed documentation. Features include support for Windows Vista & 2007
Microsoft Office, team authoring, plus more. http://www.DocToHelp.com/TechwrlList
True single source, conditional content, PDF export, modular help.
Help & Manual is the most powerful authoring tool for technical
documentation. Boost your productivity! http://www.helpandmanual.com
---
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-