| <<O>> Difference Topic Site_map (r1.22 - 25 Nov 2003 - ArthurClemens) |
| Changed: | |
| < < |
|
| > > | |
| Changed: | |
| < < | -- ArthurClemens - 10 Sep 2003 |
| > > | -- ArthurClemens - 25 Nov 2003 |
| <<O>> Difference Topic Site_map (r1.21 - 18 Sep 2003 - ArthurClemens) |
| Changed: | |
| < < |
![]() Upper part (out of 3 screen heights) of Apple's site map: www.apple.com/find/sitemap.html (11 Nov 2002), showing 3 levels of information. |
| > > |
Upper part (out of 3 screen heights) of Apple's site map: http://www.apple.com/find/sitemap.html (11 Nov 2002), showing 3 levels of information.
|
| Changed: | |
| < < | The participants also stated that they favored the categorical sitemap designs (Full & Restricted) because the information was organized into specific categories. Moreover, the Full sitemap design was considered superior to the Restricted sitemap because it was, according to the participants, easier to compare information between the categories. This was said to be more important to the participants than reducing the number of presented hyperlinks to a more manageable number. |
| > > | The participants also stated that they favored the categorical sitemap designs (Full & Restricted) because the information was organized into specific categories. Moreover, the Full sitemap design was considered superior to the Restricted sitemap because it was, according to the participants, easier to compare information between the categories. This was said to be more important to the participants than reducing the number of presented hyperlinks to a more manageable number. |
| Changed: | |
| < < |
![]() Example from L.L. Bean: www.llbean.com/siteMap/?feat=ln (10 Sep 2003). This site map uses a column layout for efficient usage of screen estate. Only three levels are shown although the site has more pages. |
| > > |
Example from L.L. Bean: http://www.llbean.com/siteMap/?feat=ln (10 Sep 2003). This site map uses a column layout for efficient usage of screen estate. Only three levels are shown although the site has more pages.
|
| Changed: | |
| < < |
![]() Example from Queensland Department of Main Roads: www.mainroads.qld.gov.au (12 Nov 2002). The dots before each link show the depth of the link. The amount of possible levels is virtually unlimited. |
| > > |
Example from Queensland Department of Main Roads: http://www.mainroads.qld.gov.au (12 Nov 2002). The dots before each link show the depth of the link. The amount of possible levels is virtually unlimited.
|
| Changed: | |
| < < |
![]() Example from Pink Roccade: www.pinkroccade.co.uk (10 Sep 2003) (design by Lost Boys). I copied the principle of Queensland, and added a page contents at the top for faster navigation. The dots (and inbetween spaces) are also part of the link, so you only have to move the mouse vertically to highlight the links. |
| > > |
Example from Pink Roccade: http://www.pinkroccade.co.uk (10 Sep 2003) (design by Lost Boys). I copied the principle of Queensland, and added a page contents at the top for faster navigation. The dots (and inbetween spaces) are also part of the link, so you only have to move the mouse vertically to highlight the links.
|
| Changed: | |
| < < |
![]() Example from Frog Design: www.frogdesign.com (15 Mar 2003). The site map page is illustrated with pieces of branding. |
| > > |
Example from Frog Design: http://www.frogdesign.com (15 Mar 2003). The site map page is illustrated with pieces of branding.
|
| Changed: | |
| < < |
![]() Example from the Association for Investment Management and Research: aimrpubs.org/site_guide.html (10 Sep 2003). This page is mentioned in [3] (design by d/D, Dynamic Diagrams, the authors' company). |
| > > |
Example from the Association for Investment Management and Research: http://aimrpubs.org/site_guide.html (10 Sep 2003). This page is mentioned in [3] (design by d/D, Dynamic Diagrams, the authors' company). |
| <<O>> Difference Topic Site_map (r1.20 - 10 Sep 2003 - ArthurClemens) |
| Changed: | |
| < < | Use a textual listing similar to a book's table of contents. Show all levels of information, not only the first 1 or 2. Do not use progressive disclosure to save space - don't be afraid to get a site map of several window heights long. Group elements by means of indenting, color and size relations. Put the link to the site map on every page and make it clearly visible, not just as secondary link at the bottom of the page. |
| > > | Use a textual listing similar to a book's table of contents. Show all levels of information, not only the first 1 or 2. Do not use progressive disclosure to save space - don't be afraid to get a site map of several window heights long. Group elements by means of indenting, color and size relations. Put the link to the site map on every page and make it clearly visible, not just as secondary link at the bottom of the page. Put links to the site map in Help and Search results. |
| Added: | |
| > > | Ecommerce as well as informational sites can benefit from a site map. |
| Changed: | |
| < < | The participants also stated that they favored the categorical sitemap designs (Full & Restricted) because the information was organized into specific categories. Moreover, the Full sitemap design was considered superior to the Restricted sitemap because it was, according to the participants, easier to compare information between the categories. This was said to be more important to the participants than reducing the number of presented hyperlinks to a more manageable number. |
| > > | The participants also stated that they favored the categorical sitemap designs (Full & Restricted) because the information was organized into specific categories. Moreover, the Full sitemap design was considered superior to the Restricted sitemap because it was, according to the participants, easier to compare information between the categories. This was said to be more important to the participants than reducing the number of presented hyperlinks to a more manageable number. |
| Changed: | |
| < < |
I noticed that CNN has removed its site map from the site. What could be the reason? Martijn van Welie writes |
| > > |
I noticed that CNN has removed its site map from the site. What could be the reason? Martijn van Welie writes |
| Changed: | |
| < < |
|
| > > |
|
| <<O>> Difference Topic Site_map (r1.19 - 10 Sep 2003 - ArthurClemens) |
| Added: | |
| > > |
Only the smallest or the biggest sites can do without a site map. If there are more pages than the main navigation shows at the homepage (not counting dropdown menus), you will need a site map.
Amazon does not have a site map - but it does have a Directory of All Stores |
| Changed: | |
| < < | |
| > > | |
| <<O>> Difference Topic Site_map (r1.18 - 10 Sep 2003 - ArthurClemens) |
| Changed: | |
| < < |
![]() |
| > > |
![]() |
| Changed: | |
| < < | I noticed that CNN has removed its site map from the site. What could be the reason? -- ArthurClemens - 10 Sep 2003 |
| > > |
I noticed that CNN has removed its site map from the site. What could be the reason? Martijn van Welie writes |
| Changed: | |
| < < |
![]() Example from Queensland Department of Main Roads, www.mainroads.qld.gov.au (12 Nov 2002). The dots before each link show the depth of the link. The amount of possible levels is virtually unlimited. |
| > > |
![]() Example from L.L. Bean: www.llbean.com/siteMap/?feat=ln (10 Sep 2003). This site map uses a column layout for efficient usage of screen estate. Only three levels are shown although the site has more pages. |
| Changed: | |
| < < |
![]() Example from Pink Roccade, www.pinkroccade.co.uk (10 Sep 2003) (design by Lost Boys). I copied the principle of Queensland, and added a page contents at the top for faster navigation. The dots (and inbetween spaces) are also part of the link, so you only have to move the mouse vertically to highlight the links. |
| > > |
![]() Example from Queensland Department of Main Roads: www.mainroads.qld.gov.au (12 Nov 2002). The dots before each link show the depth of the link. The amount of possible levels is virtually unlimited. |
| Changed: | |
| < < |
![]() Example from Frog Design, www.frogdesign.com (15 Mar 2003). The site map page is illustrated with pieces of branding. |
| > > |
![]() Example from Pink Roccade: www.pinkroccade.co.uk (10 Sep 2003) (design by Lost Boys). I copied the principle of Queensland, and added a page contents at the top for faster navigation. The dots (and inbetween spaces) are also part of the link, so you only have to move the mouse vertically to highlight the links. |
| Changed: | |
| < < |
![]() Example from aimrpubs.org (10 Sep 2003). This page is mentioned in [3] (design by d/D, Dynamic Diagrams, the authors' company). |
| > > |
![]() Example from Frog Design: www.frogdesign.com (15 Mar 2003). The site map page is illustrated with pieces of branding. ![]() Example from the Association for Investment Management and Research: aimrpubs.org/site_guide.html (10 Sep 2003). This page is mentioned in [3] (design by d/D, Dynamic Diagrams, the authors' company). |
| Added: | |
| > > | |
| Added: | |
| > > | %META:FILEATTACHMENT{name="Sitemap_LLBean_20030910.png" attr="h" comment="" date="1063220477" path="Sitemap_LLBean_20030910.png" size="287944" user="ArthurClemens" version="1.1"}% |
| <<O>> Difference Topic Site_map (r1.17 - 09 Sep 2003 - ArthurClemens) |
| Changed: | |
| < < | Upper part (out of 3 screen heights) of Apple's site map: www.apple.com/find/sitemap.html (11 Nov 2002) |
| > > | Upper part (out of 3 screen heights) of Apple's site map: www.apple.com/find/sitemap.html (11 Nov 2002), showing 3 levels of information. |
| Changed: | |
| < < | Provide conceptual overview is related to the function of a book's table of contents: the reader can quickly learn what kind of book he is holding by skimming over the chapter titles. Is it an overview, a textbook, a monograph, a scholarly study, or a novel? What subject does the book cover? Is the subject within my knowledge domain? |
| > > | Provide conceptual overview is related to the function of a book's table of contents: the reader can quickly learn what kind of book he is holding by skimming over the chapter titles. Is it an overview, a textbook, a monograph, a scholarly study, or a novel? What subject does the book cover? Is the subject within my knowledge domain? [4] |
| Changed: | |
| < < | Provide quick access is a means of navigating the site. The visitor can skip the site navigation and click directly on one of the deeper links. |
| > > | Provide quick access is a means of navigating the site. The visitor can skip the site navigation and click directly on one of the deeper links. |
| Changed: | |
| < < | A site map can only be successful if it fulfills both functions. |
| > > | A site map can only be successful if it fulfills both functions. |
| Changed: | |
| < < |
|
| > > |
SolutionUse a textual listing similar to a book's table of contents. Show all levels of information, not only the first 1 or 2. Do not use progressive disclosure to save space - don't be afraid to get a site map of several window heights long. Group elements by means of indenting, color and size relations. Put the link to the site map on every page and make it clearly visible, not just as secondary link at the bottom of the page.DiagramA drawingUse whenImplementationTypes of site map, page length |
| Changed: | |
| < < | A usability research [1] (1999) looked at 3 kinds of site map: Alphabetized Index sitemap (an index, so not really a site map), Full categorical sitemap, and Restricted categorical sitemap (where the user needs to click a topic category to see the links). |
| > > | A usability research [1] (1999) looked at 3 kinds of site map: Alphabetized Index sitemap (actually a site index), Full categorical sitemap (normal site map), and Restricted categorical sitemap (where the user needs to click a topic category to see the links; this principle is also called progressive disclosure). |
| Changed: | |
| < < | The participants also stated that they favored the categorical sitemap designs (Full & Restricted) because the information was organized into specific categories. Moreover, the Full sitemap design was considered superior to the Restricted sitemap because it was, according to the participants, easier to compare information between the categories. This was said to be more important to the participants than reducing the number of presented hyperlinks to a more manageable number. |
| > > | The participants also stated that they favored the categorical sitemap designs (Full & Restricted) because the information was organized into specific categories. Moreover, the Full sitemap design was considered superior to the Restricted sitemap because it was, according to the participants, easier to compare information between the categories. This was said to be more important to the participants than reducing the number of presented hyperlinks to a more manageable number. |
| Changed: | |
| < < | This last line is significant. Is says that users preferred a longer page that included more links, to a page with less links (with hidden link levels). |
| > > | This last line is significant too: the users preferred a longer page that included all links to a page with less links (with hidden link levels). |
| Changed: | |
| < < |
|
| > > |
Expandability |
| Changed: | |
| < < | Another research [2] (2002) investigated the trends in current web site design. By looking at all Fortune 500 web sites, the researchers found that the extended categorical site map (lists of topics 3 or more levels deep) was used most, and that graphical site maps had almost completely disappeared. |
| > > | Somewhere at the beginning of the Web, around 1996, site maps where often a designer's showcase. You could find the most diverse metaphorical imagery and novel information design displays that were used as vehicles for ideas about navigating the Web in general and that one site in particular. See Kahn [3] for a collection of site maps from this period. |
| Added: | |
| > > | Early sites were not designed for change and site maps reflected this brochure approach. Of course, when sites did grow, the static site map quickly wore out and was replaced by a textual version. By 2002 the graphical site maps had almost completely disappeared [2]. |
| Added: | |
| > > | Textual site maps are easier to change and can be generated automatically from the Content Management System or database. |
| Changed: | |
| < < |
SolutionThe solution... |
| > > |
Spatial metaphores |
| Changed: | |
| < < |
DiagramA drawing |
| > > | Kahn [3] distinguishes 4 types of site map: lists, progressive disclosure, circles and metaphor. He writes about circle site maps: |
| Changed: | |
| < < |
Use when |
| > > |
The same information that can be presented as a hierarchical list or indented outline can also be presented as a series of layers around a central point. Circular organization carries with it an implied meaning. In terms of the visual impact of the map, the starting point (usually the Home Page) is at the center of the focus, rather than at the top left of a long list of items. A circular organization can be a very efficient way to present information. (p. 86)
|
| Changed: | |
| < < |
ImplementationDetails |
| > > | Kahn is rather positive about circular displays, calling them "graphically appealing, inviting exploration and interaction". Their problem lies in the implied meaning. What does it imply that the homepage is at the center? A spatial arrangement is a misplaced metaphor in this case, because web pages are not geographically ordered. It does not give me more insight to know that Customers is to the east of the homepage. Conceptual grouping is effectively to visualize using traditional markup means such as indenting, use of color and size relations. A site map's main goal is not exploration and esthetic pleasure. It should give insight in a site's content and be quick to navigate. |
| Added: | |
| > > | I noticed that CNN has removed its site map from the site. What could be the reason? -- ArthurClemens - 10 Sep 2003 |
| Changed: | |
| < < |
put image here Example from xxx. |
| > > |
![]() Example from Queensland Department of Main Roads, www.mainroads.qld.gov.au (12 Nov 2002). The dots before each link show the depth of the link. The amount of possible levels is virtually unlimited. ![]() Example from Pink Roccade, www.pinkroccade.co.uk (10 Sep 2003) (design by Lost Boys). I copied the principle of Queensland, and added a page contents at the top for faster navigation. The dots (and inbetween spaces) are also part of the link, so you only have to move the mouse vertically to highlight the links. ![]() Example from Frog Design, www.frogdesign.com (15 Mar 2003). The site map page is illustrated with pieces of branding. ![]() Example from aimrpubs.org (10 Sep 2003). This page is mentioned in [3] (design by d/D, Dynamic Diagrams, the authors' company). |
| Changed: | |
| < < |
|
| > > |
|
| Added: | |
| > > |
|
| Changed: | |
| < < | -- ArthurClemens - 12 Aug 2003 |
| > > | -- ArthurClemens - 10 Sep 2003 |
| Added: | |
| > > | %META:FILEATTACHMENT{name="Sitemap_FrogDesign_20030315.png" attr="h" comment="" date="1063204135" path="Sitemap_FrogDesign_20030315.png" size="124696" user="ArthurClemens" version="1.1"}% %META:FILEATTACHMENT{name="Sitemap_Queensland_20021112.png" attr="h" comment="" date="1063204643" path="Sitemap_Queensland_20021112.png" size="61237" user="ArthurClemens" version="1.1"}% %META:FILEATTACHMENT{name="Sitemap_PinkRoccade_uk_20030910.png" attr="h" comment="" date="1063207797" path="Sitemap_PinkRoccade_uk_20030910.png" size="56470" user="ArthurClemens" version="1.1"}% %META:FILEATTACHMENT{name="Sitemap_aimrpubs.org.png" attr="h" comment="" date="1063208104" path="Sitemap_aimrpubs.org.png" size="168181" user="ArthurClemens" version="1.1"}% |
| <<O>> Difference Topic Site_map (r1.16 - 12 Aug 2003 - ArthurClemens) |
| Changed: | |
| < < |
|
| > > |
|
| Changed: | |
| < < | Provide conceptual overview is related to the function of a book's table of contents. Skimming over the chapter titles, the reader can quickly learn what kind of book he is holding (an overview, a textbook, a monograph, a scholarly study, a novel, etc.), and what material the book covers. |
| > > | Provide conceptual overview is related to the function of a book's table of contents: the reader can quickly learn what kind of book he is holding by skimming over the chapter titles. Is it an overview, a textbook, a monograph, a scholarly study, or a novel? What subject does the book cover? Is the subject within my knowledge domain? |
| Changed: | |
| < < | Similarly, a site map shows the site's scope and depth in a glance. |
| > > | Similarly, a site map shows the site's scope and depth: the visitor learns what the site is about and how of the subject it covers. |
| Changed: | |
| < < | Provide quick access is a means of navigating the site. |
| > > | Provide quick access is a means of navigating the site. The visitor can skip the site navigation and click directly on one of the deeper links. |
| Changed: | |
| < < | A usability research [1] (1999) looked at 3 kinds of site map: Alphabetized Index sitemap (an index, not really a site map), Full categorical sitemap, and Restricted categorical sitemap (where the user needs to click a topic category to see the links). |
| > > | A usability research [1] (1999) looked at 3 kinds of site map: Alphabetized Index sitemap (an index, so not really a site map), Full categorical sitemap, and Restricted categorical sitemap (where the user needs to click a topic category to see the links). |
| Deleted: | |
| < < | Our results found that the Full and Restricted categorical sitemaps had significantly higher numbers of successful searches (fewer failed attempts) than the Alphabetized sitemap. In addition, users had significantly higher perceptions of ease-of-use for Full and Restricted sitemaps over the Alphabetized sitemap (see Figure 4). They were also significantly more satisfied and found the searches to be easier with the Full and Restricted sitemaps than with the Alphabetized sitemap. In the ranking of the three sitemap designs, the Full sitemap was most preferred. |
| Changed: | |
| < < | Another research [2] (2002) investigated the trends in current web site design. It found that the extended categorical site map (lists of topics 3 or more levels deep) was used most: |
| > > | Another research [2] (2002) investigated the trends in current web site design. By looking at all Fortune 500 web sites, the researchers found that the extended categorical site map (lists of topics 3 or more levels deep) was used most, and that graphical site maps had almost completely disappeared. |
| Deleted: | |
| < < |
Clearly the categorical style was the most popular. The hierarchical and graphical method of designing of a sitemap were found less frequently (less than 5% of the time). Interestingly, there were no graphical sitemaps found that used anything more elaborate than basic shapes. For example, we thought some sites might make use of symbols, cartoons or pictures to represent the site content. The closest thing we found to these possibilities were actually home pages with animated graphics and link labels. Surprisingly, both of these sites used categorical listings for their actual sitemap pages.
|
| Changed: | |
| < < | -- ArthurClemens - 29 Jul 2003 |
| > > | -- ArthurClemens - 12 Aug 2003 |
| <<O>> Difference Topic Site_map (r1.15 - 30 Jul 2003 - ArthurClemens) |
| Changed: | |
| < < | A site map has 2 basic uses: |
| > > | A site map has 2 basic functions: |
| Changed: | |
| < < | Provide conceptual overview is related to the function of a book's table of contents. The table of contents gives a broad overview of the material the book covers. And skimming over the chapter titles, the reader can quickly learn what kind of book he is holding: an overview, a textbook, a monograph, a scholarly study, a novel. |
| > > | Provide conceptual overview is related to the function of a book's table of contents. Skimming over the chapter titles, the reader can quickly learn what kind of book he is holding (an overview, a textbook, a monograph, a scholarly study, a novel, etc.), and what material the book covers. |
| Added: | |
| > > |
A site map can only be successful if it fulfills both functions.
A usability research [1] (1999) looked at 3 kinds of site map: Alphabetized Index sitemap (an index, not really a site map), Full categorical sitemap, and Restricted categorical sitemap (where the user needs to click a topic category to see the links). Not surprisingly, the Alphabetized Index sitemap proved less useful (regarding the task the users where asked to perform).
Our results found that the Full and Restricted categorical sitemaps had significantly higher numbers of successful searches (fewer failed attempts) than the Alphabetized sitemap. In addition, users had significantly higher perceptions of ease-of-use for Full and Restricted sitemaps over the Alphabetized sitemap (see Figure 4). They were also significantly more satisfied and found the searches to be easier with the Full and Restricted sitemaps than with the Alphabetized sitemap. In the ranking of the three sitemap designs, the Full sitemap was most preferred.
The participants also stated that they favored the categorical sitemap designs (Full & Restricted) because the information was organized into specific categories. Moreover, the Full sitemap design was considered superior to the Restricted sitemap because it was, according to the participants, easier to compare information between the categories. This was said to be more important to the participants than reducing the number of presented hyperlinks to a more manageable number.
This last line is significant. Is says that users preferred a longer page that included more links, to a page with less links (with hidden link levels).
Another research [2] (2002) investigated the trends in current web site design. It found that the extended categorical site map (lists of topics 3 or more levels deep) was used most:
Clearly the categorical style was the most popular. The hierarchical and graphical method of designing of a sitemap were found less frequently (less than 5% of the time). Interestingly, there were no graphical sitemaps found that used anything more elaborate than basic shapes. For example, we thought some sites might make use of symbols, cartoons or pictures to represent the site content. The closest thing we found to these possibilities were actually home pages with animated graphics and link labels. Surprisingly, both of these sites used categorical listings for their actual sitemap pages.
|
| Deleted: | |
| < < |
PrincipleSelection, navigation, ... |
| Changed: | |
| < < | |
| > > |
|
| <<O>> Difference Topic Site_map (r1.14 - 27 Jul 2003 - ArthurClemens) |
| Changed: | |
| < < | Also known as: Sitemap, Contents |
| > > | Also known as: Sitemap, Table of Contents, Contents, Site guide |
| Changed: | |
| < < |
put image here Example from xxx. |
| > > |
![]() Upper part (out of 3 screen heights) of Apple's site map: www.apple.com/find/sitemap.html (11 Nov 2002) |
| Changed: | |
| < < | What is the problem that this pattern solves? |
| > > | Site maps come in all sorts of forms. However, only a few actually work. |
| Added: | |
| > > |
A site map has 2 basic uses:
|
| Added: | |
| > > |
|
| Changed: | |
| < < | -- ArthurClemens - 26 Jul 2003 |
| > > | -- ArthurClemens - 29 Jul 2003 |
| Changed: | |
| < < | %META:TOPICMOVED{by="guest" date="1037314694" from="Patterns.TableOfContents" to="Patterns.Table_of_contents"}% |
| > > | %META:FILEATTACHMENT{name="appl1.png" attr="h" comment="" date="1059340838" path="appl1.png" size="96907" user="ArthurClemens" version="1.1"}% %META:TOPICMOVED{by="ArthurClemens" date="1059331004" from="Patterns.Table_of_contents" to="Patterns.Site_map"}% |
| <<O>> Difference Topic Site_map (r1.13 - 26 Jul 2003 - ArthurClemens) |
| Changed: | |
| < < |
! Abstract pattern |
| > > | Also known as: Sitemap, Contents |
| Changed: | |
| < < | Also known as: Site map. |
| > > |
put image here
Example from xxx. |
| Deleted: | |
| < < | Concrete implementations of this pattern: |
| Changed: | |
| < < |
Related information: |
| > > |
ProblemWhat is the problem that this pattern solves?MotivationSolutionThe solution...DiagramA drawingPrincipleSelection, navigation, ...Use whenImplementationDetailsDiscussionExamples
put image here
Example from xxx. ConnectionsRelations to higher and lower patternsLiterature |
| Deleted: | |
| < < |
DiscussionThe term "map" refers too much to real world graphical maps. So my idea is you have 2 kinds of Tables of contents: a graphical map and a listing (Listing could be called "Contents" in a menu). |
| Changed: | |
| < < | -- ArthurClemens - 03 Jul 2003 |
| > > | -- ArthurClemens - 26 Jul 2003 |
| Changed: | |
| < < | %META:FIELD{name="Subtitle" title="Subtitle" value="Abstract pattern"}% |
| > > | %META:FIELD{name="Subtitle" title="Subtitle" value=""}% |
| <<O>> Difference Topic Site_map (r1.12 - 03 Jul 2003 - ArthurClemens) |
| Changed: | |
| < < | Material: Table of contents material |
| > > |
! Abstract pattern |
| Changed: | |
| < < | Also known as: site map |
| > > | Also known as: Site map. |
| Changed: | |
| < < |
The problem with renaming is that Site map is such a familiar word for online users. Still, I would prefer to introduce names that do not evoke a wrong mapping, to speak with Donald Norman. |
| > > |
DiscussionThe term "map" refers too much to real world graphical maps. So my idea is you have 2 kinds of Tables of contents: a graphical map and a listing (Listing could be called "Contents" in a menu). |
| Changed: | |
| < < | -- ArthurClemens - 11 Feb 2003 |
| > > |
-- ArthurClemens - 03 Jul 2003 |
| Changed: | |
| < < | %META:FIELD{name="Title" title="Title" value="Table of contents"}% |
| > > | %META:FIELD{name="Title" title="Title" value=""}% |
| <<O>> Difference Topic Site_map (r1.11 - 11 Feb 2003 - ArthurClemens) |
| Changed: | |
| < < |
Site mapAbstract pattern Material: Table of contents material |
| > > | Material: Table of contents material |
| Changed: | |
| < < | 2 Concrete implementations of this pattern: |
| > > | Concrete implementations of this pattern: |
| Changed: | |
| < < |
Jakob Nielsen's Alertbox, January 6, 2002 cached page |
| > > | Jakob Nielsen's Alertbox, January 6, 2002 (cached page) |
| Changed: | |
| < < |
I renamed "Site map" to "Table of contents" because "map" refers too much to real world graphical maps. For the latter I would use "Table of contents (Graphical map)". In a menu it could also be called Contents. |
| > > |
|
| Changed: | |
| < < | Still, I would prefer to introduce names that do not evoke wrong mappings, to speak with Donald Norman. |
| > > | Still, I would prefer to introduce names that do not evoke a wrong mapping, to speak with Donald Norman. |
| Added: | |
| > > | -- ArthurClemens - 11 Feb 2003 |
| Changed: | |
| < < | -- ArthurClemens - 31 Jan 2003 |
| > > | %META:FORM{name="Title_form"}% %META:FIELD{name="Title" title="Title" value="Table of contents"}% %META:FIELD{name="Subtitle" title="Subtitle" value="Abstract pattern"}% |
| <<O>> Difference Topic Site_map (r1.10 - 30 Jan 2003 - ArthurClemens) |
| Added: | ||||||||||||
| > > | Abstract pattern | |||||||||||
| Changed: | ||||||||||||
| < < | Material: Table of contents material | |||||||||||
| > > | Material: Table of contents material | |||||||||||
| Changed: | ||||||||||||
| < < |
| |||||||||||
| > > | 2 Concrete implementations of this pattern: | |||||||||||
| Changed: | ||||||||||||
| < < |
Used literatureReference literature | |||||||||||
| > > |
Related information: | |||||||||||
| Deleted: | ||||||||||||
| < < | (available at my desk -- ArthurClemens) | |||||||||||
| Changed: | ||||||||||||
| < < | -- ArthurClemens - 29 Jan 2003 | |||||||||||
| > > |
I renamed "Site map" to "Table of contents" because "map" refers too much to real world graphical maps. For the latter I would use "Table of contents (Graphical map)". In a menu it could also be called Contents. The problem with renaming is that Site map is such a familiar word for online users. Still, I would prefer to introduce names that do not evoke wrong mappings, to speak with Donald Norman. -- ArthurClemens - 31 Jan 2003 | |||||||||||
| <<O>> Difference Topic Site_map (r1.9 - 29 Jan 2003 - ArthurClemens) |
| Changed: | |
| < < |
Table of contents |
| > > |
Site map |
| Added: | |
| > > | Concrete implementations of this pattern: |
| Changed: | |
| < < |
Jakob Nielsen's Alertbox, January 6, 2002 cached page
|
| > > |
Jakob Nielsen's Alertbox, January 6, 2002 cached page
|
| Added: | |
| > > | (available at my desk -- ArthurClemens) |
| Changed: | |
| < < |
Concrete implementations of this pattern |
| > > | -- ArthurClemens - 29 Jan 2003 |
| <<O>> Difference Topic Site_map (r1.8 - 25 Nov 2002 - TWikiGuest) |
| Added: | |
| > > | Material: Table of contents material |
| <<O>> Difference Topic Site_map (r1.7 - 17 Nov 2002 - TWikiGuest) |
| Changed: | ||||
| < < | Also known as: Sitemap | |||
| > > | Also known as: site map | |||
| Changed: | ||||
| < < |
| |||
| > > |
| |||
| <<O>> Difference Topic Site_map (r1.6 - 14 Nov 2002 - TWikiGuest) |
| Changed: | |||
| < < | %META:TOPICPARENT{name="NavigationPattern"}% | ||
| > > | %META:TOPICPARENT{name="Navigation_"}% | ||
| Changed: | |||
| < < |
| ||
| > > |
| ||
| Changed: | |||
| < < |
| ||
| > > |
| ||
| Changed: | |||
| < < |
| ||
| > > |
| ||
| Changed: | |||
| < < | |||
| > > | |||
| Added: | |||
| > > | %META:TOPICMOVED{by="guest" date="1037314694" from="Patterns.TableOfContents" to="Patterns.Table_of_contents"}% | ||
| <<O>> Difference Topic Site_map (r1.5 - 12 Nov 2002 - TWikiGuest) |
| <<O>> Difference Topic Site_map (r1.4 - 12 Nov 2002 - TWikiGuest) |
| Changed: | |
| < < |
Literature |
| > > |
Used literatureReference literature |
| <<O>> Difference Topic Site_map (r1.3 - 12 Nov 2002 - TWikiGuest) |
| Added: | |
| > > | Also known as: Sitemap |
| Changed: | |
| < < | See for concrete implementation: |
| > > |
Literature
Concrete implementations |
| Changed: | |
| < < | %META:FORM{name="WebForm"}% |
| > > | %META:FORM{name="ClassificationForm"}% |
| <<O>> Difference Topic Site_map (r1.2 - 12 Nov 2002 - TWikiGuest) |
| Added: | |
| > > | See for concrete implementation: |
| <<O>> Difference Topic Site_map (r1.1 - 11 Nov 2002 - TWikiGuest) |
| Added: | ||||||||||||||
| > > |
%META:TOPICINFO{author="guest" date="1037057100" format="1.0" version="1.1"}%
%META:TOPICPARENT{name="NavigationPattern"}%
Table of contents
| |||||||||||||
|
Revision r1.1 - 11 Nov 2002 - 23:25 GMT - TWikiGuest Revision r1.22 - 25 Nov 2003 - 23:59 GMT - ArthurClemens |
Copyright © 2003 by the contributing authors. All material on this collaboration tool is the property of the contributing authors. Ideas, requests, problems regarding TWiki? Send feedback |