<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: Simplifying The Guardian&#8217;s header</title>
	<atom:link href="http://leonpaternoster.com/2008/09/simplifying-the-guardians-header/feed/" rel="self" type="application/rss+xml" />
	<link>http://leonpaternoster.com/2008/09/simplifying-the-guardians-header/</link>
	<description>Web writing, planning and design from Ipswich, Suffolk</description>
	<lastBuildDate>Wed, 28 Jul 2010 12:13:50 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: Leon</title>
		<link>http://leonpaternoster.com/2008/09/simplifying-the-guardians-header/comment-page-1/#comment-33794</link>
		<dc:creator>Leon</dc:creator>
		<pubDate>Wed, 09 Jun 2010 15:49:36 +0000</pubDate>
		<guid isPermaLink="false">http://leonpaternoster.com/2008/09/simplifying-the-guardians-header/#comment-33794</guid>
		<description>OK, let&#039;s get rid of Business &lt;em&gt;and&lt;/em&gt; G2 so we only have five top level nav options (you can see where this is going &#8230;)

I agree about designing for browsing scenarios: categorising content is perhaps more useful to site designers than visitors.

I&#039;m guessing the main scenarios are:

&#183; visitor has clicked on a link to a story and reads away
&#183; visitor has come via a search engine &#8212; it&#039;s &lt;em&gt;probably&lt;/em&gt; the right page but they may need some help finding the exact page they need
&#183; visitor knows the story is on the site and enters a search term (requires a really good site search engine)
&#183; visitor is interested in a subject and enters a search term (ditto)
&#183; visitor just wants to browse the news (requires a well laid out home page)
&#183; visitor wants to read stuff from a particular section (football, for example); top level nav is important

So having a really good search engine and providing relevant contextual links is perhaps the most important thing (or just making sure inline links are relevant and well labelled). I like the idea of categorising content around stories rather than newspaper sections.</description>
		<content:encoded><![CDATA[<p>OK, let&#8217;s get rid of Business <em>and</em> G2 so we only have five top level nav options (you can see where this is going &hellip;)</p>
<p>I agree about designing for browsing scenarios: categorising content is perhaps more useful to site designers than visitors.</p>
<p>I&#8217;m guessing the main scenarios are:</p>
<p>&middot; visitor has clicked on a link to a story and reads away<br />
&middot; visitor has come via a search engine &mdash; it&#8217;s <em>probably</em> the right page but they may need some help finding the exact page they need<br />
&middot; visitor knows the story is on the site and enters a search term (requires a really good site search engine)<br />
&middot; visitor is interested in a subject and enters a search term (ditto)<br />
&middot; visitor just wants to browse the news (requires a well laid out home page)<br />
&middot; visitor wants to read stuff from a particular section (football, for example); top level nav is important</p>
<p>So having a really good search engine and providing relevant contextual links is perhaps the most important thing (or just making sure inline links are relevant and well labelled). I like the idea of categorising content around stories rather than newspaper sections.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Karen</title>
		<link>http://leonpaternoster.com/2008/09/simplifying-the-guardians-header/comment-page-1/#comment-33792</link>
		<dc:creator>Karen</dc:creator>
		<pubDate>Wed, 09 Jun 2010 15:16:53 +0000</pubDate>
		<guid isPermaLink="false">http://leonpaternoster.com/2008/09/simplifying-the-guardians-header/#comment-33792</guid>
		<description>I remembering working through a whole load of browsing scenarios when we were doing one of the BBC navigation redesigns and kept coming back to the conclusion &quot;these person really should have just searched for this&quot;. 

Now admittedly there are people who have reasons/needs to browse rather than search but I do think we&#039;re all still a bit hung up on trying to provide a comprehensive, fair top-level navigation that can be used to find *all* content. That route usually results in either nav bloat or cryptic nav. Either way, underused nav. 

I think we need to get better at using this space on websites to just provide a solution to key browsing scenarios and use other tools (search, homepage space, cross-content navigation) to support others. 

(still not sure about business though ;-)</description>
		<content:encoded><![CDATA[<p>I remembering working through a whole load of browsing scenarios when we were doing one of the BBC navigation redesigns and kept coming back to the conclusion &#8220;these person really should have just searched for this&#8221;. </p>
<p>Now admittedly there are people who have reasons/needs to browse rather than search but I do think we&#8217;re all still a bit hung up on trying to provide a comprehensive, fair top-level navigation that can be used to find *all* content. That route usually results in either nav bloat or cryptic nav. Either way, underused nav. </p>
<p>I think we need to get better at using this space on websites to just provide a solution to key browsing scenarios and use other tools (search, homepage space, cross-content navigation) to support others. </p>
<p>(still not sure about business though <img src='http://leonpaternoster.com/wp-includes/images/smilies/icon_wink.gif' alt=';-)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Leon</title>
		<link>http://leonpaternoster.com/2008/09/simplifying-the-guardians-header/comment-page-1/#comment-33790</link>
		<dc:creator>Leon</dc:creator>
		<pubDate>Wed, 09 Jun 2010 13:03:13 +0000</pubDate>
		<guid isPermaLink="false">http://leonpaternoster.com/2008/09/simplifying-the-guardians-header/#comment-33790</guid>
		<description>Thanks for your comment. G2&#039;s difficult, although most broadsheet newspapers have some kind of magazine insert or section. I guess it could be given a more generic label (erm, &lt;em&gt;Magazine&lt;/em&gt;, perhaps?) or the content could be shifted to other sections; mainly to &lt;em&gt;Comment&lt;/em&gt; (which could perhaps be renamed &lt;em&gt;Comment and analysis&lt;/em&gt; or &lt;em&gt;Comment and reviews&lt;/em&gt; to make it a bit more inclusive).

Similarly, most newspapers &#8212; even red tops &#8212; have some sort of &lt;em&gt;Business&lt;/em&gt; section which serves a purpose beyond reporting business news; it may list prices or provide advice, so I think a discrete section is justifiable.

I wonder how often a newspaper&#039;s navigation menu is actually used? And what about stories that could be placed in more than one category?</description>
		<content:encoded><![CDATA[<p>Thanks for your comment. G2&#8242;s difficult, although most broadsheet newspapers have some kind of magazine insert or section. I guess it could be given a more generic label (erm, <em>Magazine</em>, perhaps?) or the content could be shifted to other sections; mainly to <em>Comment</em> (which could perhaps be renamed <em>Comment and analysis</em> or <em>Comment and reviews</em> to make it a bit more inclusive).</p>
<p>Similarly, most newspapers &mdash; even red tops &mdash; have some sort of <em>Business</em> section which serves a purpose beyond reporting business news; it may list prices or provide advice, so I think a discrete section is justifiable.</p>
<p>I wonder how often a newspaper&#8217;s navigation menu is actually used? And what about stories that could be placed in more than one category?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Karen</title>
		<link>http://leonpaternoster.com/2008/09/simplifying-the-guardians-header/comment-page-1/#comment-33789</link>
		<dc:creator>Karen</dc:creator>
		<pubDate>Wed, 09 Jun 2010 12:14:29 +0000</pubDate>
		<guid isPermaLink="false">http://leonpaternoster.com/2008/09/simplifying-the-guardians-header/#comment-33789</guid>
		<description>I certainly agree with the general direction you&#039;ve gone down, if not all the details. 

I don&#039;t know if this is still true but it certainly used to be the case that a really significant chunk of the readers of the Guardian website weren&#039;t readers of the newspaper and never had been...so G2 could be a bit tricky as an option. 

What&#039;s your thinking for keeping business as a top-level option? If we&#039;re radically simplifying then why doesn&#039;t that go under news too? Why&#039;s business special?</description>
		<content:encoded><![CDATA[<p>I certainly agree with the general direction you&#8217;ve gone down, if not all the details. </p>
<p>I don&#8217;t know if this is still true but it certainly used to be the case that a really significant chunk of the readers of the Guardian website weren&#8217;t readers of the newspaper and never had been&#8230;so G2 could be a bit tricky as an option. </p>
<p>What&#8217;s your thinking for keeping business as a top-level option? If we&#8217;re radically simplifying then why doesn&#8217;t that go under news too? Why&#8217;s business special?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Online newspaper layout: 10 years and 10 steps back &#187; Positively Deranged</title>
		<link>http://leonpaternoster.com/2008/09/simplifying-the-guardians-header/comment-page-1/#comment-26286</link>
		<dc:creator>Online newspaper layout: 10 years and 10 steps back &#187; Positively Deranged</dc:creator>
		<pubDate>Sun, 28 Jun 2009 10:42:54 +0000</pubDate>
		<guid isPermaLink="false">http://leonpaternoster.com/2008/09/simplifying-the-guardians-header/#comment-26286</guid>
		<description>[...] The Guardian&#8217;s website has a header navbar with 25 links. The print version is divided into six clear sections: news, sport, business, commentary, listings and G2. By dividing the website into a manageable [...]</description>
		<content:encoded><![CDATA[<p>[...] The Guardian&#8217;s website has a header navbar with 25 links. The print version is divided into six clear sections: news, sport, business, commentary, listings and G2. By dividing the website into a manageable [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gigantic &#8212; Why use grids?</title>
		<link>http://leonpaternoster.com/2008/09/simplifying-the-guardians-header/comment-page-1/#comment-2437</link>
		<dc:creator>Gigantic &#8212; Why use grids?</dc:creator>
		<pubDate>Tue, 06 Jan 2009 15:23:00 +0000</pubDate>
		<guid isPermaLink="false">http://leonpaternoster.com/2008/09/simplifying-the-guardians-header/#comment-2437</guid>
		<description>[...] here: newspapers should look to reduce the amount of content they place on their front pages (I&#8217;ve discussed this in relation to The Guardian).  In a sense, the use of a grid is exacerbating the fundamental [...]</description>
		<content:encoded><![CDATA[<p>[...] here: newspapers should look to reduce the amount of content they place on their front pages (I&#8217;ve discussed this in relation to The Guardian).  In a sense, the use of a grid is exacerbating the fundamental [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Leon</title>
		<link>http://leonpaternoster.com/2008/09/simplifying-the-guardians-header/comment-page-1/#comment-2295</link>
		<dc:creator>Leon</dc:creator>
		<pubDate>Sun, 28 Dec 2008 10:48:20 +0000</pubDate>
		<guid isPermaLink="false">http://leonpaternoster.com/2008/09/simplifying-the-guardians-header/#comment-2295</guid>
		<description>&lt;blockquote&gt;your version would require more clicks from the user to get to the relevant pages/articles&lt;/blockquote&gt;

Yes, it would. The challenge is to make the path to that content as clear as possible; that&#039;s why I&#039;ve used the print version of the paper as a basis for the site structure: it&#039;s logical and (Guardian) readers will be familiar with it.

The alternative is to place 50+ links on the page and hope that the reader is willing to scan for content.</description>
		<content:encoded><![CDATA[<blockquote><p>your version would require more clicks from the user to get to the relevant pages/articles</p></blockquote>
<p>Yes, it would. The challenge is to make the path to that content as clear as possible; that&#8217;s why I&#8217;ve used the print version of the paper as a basis for the site structure: it&#8217;s logical and (Guardian) readers will be familiar with it.</p>
<p>The alternative is to place 50+ links on the page and hope that the reader is willing to scan for content.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Leon</title>
		<link>http://leonpaternoster.com/2008/09/simplifying-the-guardians-header/comment-page-1/#comment-1948</link>
		<dc:creator>Leon</dc:creator>
		<pubDate>Fri, 12 Dec 2008 20:39:02 +0000</pubDate>
		<guid isPermaLink="false">http://leonpaternoster.com/2008/09/simplifying-the-guardians-header/#comment-1948</guid>
		<description>Hi Jay,

More money doesn&#039;t necessarily make it better.

&lt;em&gt;How&lt;/em&gt; is my version &#039;worse&#039;?

Ta,

Leon</description>
		<content:encoded><![CDATA[<p>Hi Jay,</p>
<p>More money doesn&#8217;t necessarily make it better.</p>
<p><em>How</em> is my version &#8216;worse&#8217;?</p>
<p>Ta,</p>
<p>Leon</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jay Vincent</title>
		<link>http://leonpaternoster.com/2008/09/simplifying-the-guardians-header/comment-page-1/#comment-1940</link>
		<dc:creator>Jay Vincent</dc:creator>
		<pubDate>Fri, 12 Dec 2008 12:26:02 +0000</pubDate>
		<guid isPermaLink="false">http://leonpaternoster.com/2008/09/simplifying-the-guardians-header/#comment-1940</guid>
		<description>That&#039;s crazy!

Your version completely ignores so many of the excellent features the guardian site employs to make their site accessible, usable and easily-navigated through. And there is soooo much content on the guardian site, your version would require more clicks from the user to get to the relevant pages/articles.

Pretty much everything you&#039;ve done is worse. The design and development of the guardian was a multi-million pound job given to one of the top media agencies in the world, so much thought and planning went into the header and site structure. I don&#039;t think you should try and &#039;improve&#039; on that.</description>
		<content:encoded><![CDATA[<p>That&#8217;s crazy!</p>
<p>Your version completely ignores so many of the excellent features the guardian site employs to make their site accessible, usable and easily-navigated through. And there is soooo much content on the guardian site, your version would require more clicks from the user to get to the relevant pages/articles.</p>
<p>Pretty much everything you&#8217;ve done is worse. The design and development of the guardian was a multi-million pound job given to one of the top media agencies in the world, so much thought and planning went into the header and site structure. I don&#8217;t think you should try and &#8216;improve&#8217; on that.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Leon Paternoster &#8212; FT redesign: modern, readable and accessible</title>
		<link>http://leonpaternoster.com/2008/09/simplifying-the-guardians-header/comment-page-1/#comment-1580</link>
		<dc:creator>Leon Paternoster &#8212; FT redesign: modern, readable and accessible</dc:creator>
		<pubDate>Thu, 20 Nov 2008 20:36:37 +0000</pubDate>
		<guid isPermaLink="false">http://leonpaternoster.com/2008/09/simplifying-the-guardians-header/#comment-1580</guid>
		<description>[...] All nonsense, of course, and the design should be saluted for breaking from the current convention for super-complex grids, content-overload and headers stuffed with 75 links. [...]</description>
		<content:encoded><![CDATA[<p>[...] All nonsense, of course, and the design should be saluted for breaking from the current convention for super-complex grids, content-overload and headers stuffed with 75 links. [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
