How to Design a Table of Contents
By Steve Toub
There's something in our human nature that makes us want to dive into things, to browse, to dabble. We first try to program our VCRs without looking at the manual. We drive for awhile; if we get lost, we look at a map or ask directions (or not, depending on our gender).
When we visit a Web site, we dive right in. We take the default path through the site, stopping for instructions or directions only when we're confused, when we're tired of browsing, or when we have a very specific task to complete. At these times, we often depend on a table of contents. (I frequently use the phrase "table of contents," but other terms such as "contents," "site contents," and "site map" are acceptable and often preferable on the Web.)
A contents page provides an overview of the entirety of content. Since a table of contents represents the way a document collection is organized, it shows the way content is grouped and labeled, and it shows the relationships between those content elements. It also lets users navigate to find particular areas. A table of contents in a print publication or a map in a shopping mall merely points you to a certain location. Hyperlinks on a Web table of contents transport users immediately. The structure of a table of contents also facilitates serendipitous browsing, similar to what happens when you look up a book in the library, and find that the books on the shelf nearby are more relevant to you than the one you initially sought.
A table of contents is an effective tool to quickly explain what the site is for and why users may want to visit.
