nEntries can be listed under separate category headings. For example, reference entries and procedural entries can be separated (Figure 4.1).The purpose of the main Contents screen is to present an overview of the information contained in Help and to provide a clear, logical path to information. The Help Contents functions similarly to a table of contents in a book and should follow a similar model. Users are encouraged to use Search, or a separate online index, when they want to look up information as they would in a book index.
Sublevel Contents screens provide a path from the main Contents to individual Help topics. Category entries on the main Contents screen jump to sublevel Contents screens that list either Help topics in that category or other sublevel Contents screens.
nEntries can be listed under separate category headings. For example, reference entries and procedural entries can be separated (Figure 4.1).
nEntries are presented by category, either as text jumps and/or “hot” bitmaps. List entries should be in learning-path order by frequency of use, or alphabetically (Figure 4.2 shows categories listed in learning-path order).
nThe list of entries on the main Contents screen should be 10 items or fewer. Avoid having more than 15 entries if possible. If your list is longer than 15 entries, you should rethink your Help organization.
nAvoid deeply nested sublevels so the user doesn’t have to jump more than two or three times to display a Help topic.
nOn sublevel Contents screens with entries that jump to individual Help topics, avoid long scrolling lists.