For instance, a software company might only have two or
three pages inside the About Us section, but 500 pages inside the knowledgebase of their
support portal.
A site map must maintain a balance between usability and comprehensiveness. Since a site
map is relegated to a single HTML page, it has to present the breadth of the site without
overwhelming the user. Present too little (or too high-level) content and its purpose is
defeated; list 9,475 pages spanning 192 sections and you??™ll do nothing but send cursors
sprinting for the nearest exit link. At the very least, all major sections should be represented
with some level of detail, whether that includes individual pages or just important
subcategories.
In a blow to the old site map??™s ego, studies have revealed that users can (and will) find the
content they want more quickly using a site??™s search engine than by browsing. This makes
sense. After all, it??™s easier to flip to the index of a book and look up a keyword than to pick
through a preordered list of content, no matter how intelligently designed. The former
empowers the end-user; the latter empowers the original author.
Pages:
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206