Re: Contents at a Glance

[Sella Rush <SellaR -at- APPTECHSYS -dot- COM>]

Agree, Beth.  I tend to use a contents with only 2 heading levels, an
index, obvious headings in the text for easy browsing, and then a
bulleted task-oriented summary at the beginning of each chapter.  I also
make sure that there's an index entry for every 3rd or lower heading.

So I guess you could say I use an "at a glance" contents but not an
exhaustive one.  This is because I tend to buy into that whole schema
theory--give'em a raw structure on which to hang new knowledge.
++++++++++++++++++++++++++++++++++
Sella Rush
sellar -at- apptechsys -dot- com
Applied Technical Systems, Inc. (ATS)
Bremerton, Washington USA
Developers of the CCM Database


> You don't necessarily want to give them the Contents as an idea of
> whether
> their particular need is met by the manual, and where to find that
> information. To my mind, an exhaustive Table of Contents is much less
> effective than about a dozen other ways of conveying information.
>
> --Beth
> Beth Agnew
>

 TECHWR-L (Technical Communication) List Information: To send a message
to 2500+ readers, e-mail to TECHWR-L -at- LISTSERV -dot- OKSTATE -dot- EDU -dot-  Send commands
   to LISTSERV -at- LISTSERV -dot- OKSTATE -dot- EDU (e.g. HELP or SIGNOFF TECHWR-L).
  Search the archives at http://www.documentation.com/  or search and
browse the archives at http://listserv.okstate.edu/archives/techwr-l.html