%META:TOPICPARENT{name="Table_of_contents"}%

%META:TOPICPARENT{name="Repository_materials"}%

Rewrite (from Nielsen):

Jacob Nielsen wrote in his Alertbox, January 6, 2002:

-- ArthurClemens - 31 Jan 2003

%META:FORM{name="Title_form"}% %META:FIELD{name="Title" title="Title" value="Table of contents material"}% %META:FIELD{name="Subtitle" title="Subtitle" value=""}%

Table of contents material

%META:FORM{name="Title_form"}% %META:FIELD{name="Title" title="Title" value="Table of contents material"}% %META:FIELD{name="Subtitle" title="Subtitle" value=""}%

%META:TOPICPARENT{name="Table_of_contents"}%

To write
Call the page Site map as this name is widely used and known by users.

Rewrite (from Nielsen):

A site map's main benefit is to give users an overview of the site's areas in a single glance by dedicating an entire page to a visualization of the information architecture. If designed well, this overview can include several levels of hierarchy, and yet not be so big that users lose their ability to grasp the map as a whole. Some of the site maps we studied stretched over six screens on a standard 800x600 monitor. This is much too much. We recommend keeping the site map short; it should be no more than two-and-a-half times the window size most common among your users.

The greatest failures in our study came from site maps that attempted to lure the user into a dynamically twisting and expanding view, rather than presenting a simple, static representation of the information architecture. The site map's goal is to give users a single overview of the information space. If users have to work to reveal different parts of the map, that benefit is lost.

Dynamic site maps are basically an alternative way of navigating through the information space using a set of non-standard interaction techniques. For example, one site used a hyperbolic tree, where users had to click and drag clusters of links around the screen to expand areas of interest. Nobody could do this well.

A site map should not be a navigational challenge of its own. It should be a map.

-- ArthurClemens - 31 Jan 2003

-- TWikiGuest - 23 Nov 2002

%META:TOPICINFO{author="guest" date="1038265920" format="1.0" version="1.1"}%

Table of contents material

Pattern: Table of contents?

A Sitemap on Every Page

• http://www.webword.com/reports/sitemap.html

-- TWikiGuest - 23 Nov 2002