<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Navigation on Andy Beaumont</title>
    <link>https://andybeaumont.com/tags/navigation/</link>
    <description>Recent content in Navigation on Andy Beaumont</description>
    <generator>Hugo -- gohugo.io</generator>
    <lastBuildDate>Tue, 30 Mar 2010 17:07:00 +0000</lastBuildDate>
    
	<atom:link href="https://andybeaumont.com/tags/navigation/index.xml" rel="self" type="application/rss+xml" />
    
    
    <item>
      <title>Scotch Egg Navigation</title>
      <link>https://andybeaumont.com/post/2010-03-30-scotch-egg-navigation/</link>
      <pubDate>Tue, 30 Mar 2010 17:07:00 +0000</pubDate>
      
      <guid>https://andybeaumont.com/post/2010-03-30-scotch-egg-navigation/</guid>
      <description>While working on a project with Richard Amos about a year ago we were pondering the static linear nature of breadcrumbs and wondering why they should always be so. The breadcrumb serves two purposes; firstly it gives users a sense of where they are in a site&amp;rsquo;s structure, helping them to never feel lost or disoriented. Which leads to the second purpose, to always provide them with a path home. The first of these is done entirely visually, you don&amp;rsquo;t need to click on the breadcrumb or interact with it in any way in order to help orient yourself.</description>
    </item>
    
  </channel>
</rss>