<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>DyeWeb.com &#187; Web Development</title>
	<atom:link href="http://dyeweb.com/thoughts/category/web-development/feed/" rel="self" type="application/rss+xml" />
	<link>http://dyeweb.com</link>
	<description>The blog &#38; portfolio of Scott Dye</description>
	<lastBuildDate>Thu, 26 Aug 2010 14:14:44 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.5</generator>
		<item>
		<title>Grouping Navigation Areas of a Website</title>
		<link>http://dyeweb.com/thoughts/23/grouping-navigation-areas-of-a-website/</link>
		<comments>http://dyeweb.com/thoughts/23/grouping-navigation-areas-of-a-website/#comments</comments>
		<pubDate>Mon, 19 Jun 2006 15:36:09 +0000</pubDate>
		<dc:creator>Scott</dc:creator>
				<category><![CDATA[Web Development]]></category>

		<guid isPermaLink="false">http://dyeweb.com/?p=23</guid>
		<description><![CDATA[In doing web design - especially for smaller sites and/or smaller companies - I often run into clients who want to have one list of navigation links. Since websites have such a large number of links associated with them, it is common to create multiple navigation areas, loosely grouped by priority and/or intent. It is [...]]]></description>
			<content:encoded><![CDATA[<p>In doing web design - especially for smaller sites and/or smaller companies - I often run into clients who want to have one list of navigation links.</p>
<p>Since websites have such a large number of links associated with them, it is common to create multiple navigation areas, loosely grouped by priority and/or intent. It is well documented from extensive user testing that online users â€œscanâ€ a webpage to find what they are looking for as opposed to â€œreadingâ€ it. Also, from past experience the typical user expects to find links either along the top, left, or bottom of the page.<br />
<span id="more-23"></span></p>
<p>As a list of links becomes longer (more than approx. 10 items) it is much more difficult to â€œscanâ€ the list and find a particular link â€“ the desired link gets â€œlostâ€ visually, like trying to pinpoint one particular word on an entire page of text â€“ it can be done, but you might pass by the word a couple of times before finding it. Simply put, it is easier to find what you are looking for in two groups of 5-10 links each instead of one long list of 10-20 links. </p>
<p>Larger sites (like msn.com or major news sites) have so many links that they have no option but to have long lists, but even then they try to group them as best they can. </p>
<p>On smaller sites, often there are three groups of links:</p>
<ol>
<li>the main â€œcategoryâ€ links (the main information-based sections of the site) - typically on the left or at the top of the site</li>
<li>utility links (action-oriented or interactive areas of the site) - usually at the top right of the site, smaller than the main category links</li>
<li>Footer/legal/corporate links (often including links such as â€œcorporate infoâ€, â€œemploymentâ€, â€œcontact usâ€ etc. as well as legal info)</li>
</ol>
<p>It should also be noted that a user with a specific goal in mind (like coming to the site just to send a comment or look for job postings) will typically look a little harder for a particular link than someone who is just looking for info. This allows you to emphasize the more general info links, and group them more prominently, and slightly de-emphasize the â€œspecific goalâ€ links. The end result is a site that is much easier to navigate by both types of users.</p>
]]></content:encoded>
			<wfw:commentRss>http://dyeweb.com/thoughts/23/grouping-navigation-areas-of-a-website/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

