Originally Posted by
Stomme poes
Here's the reason I don't put content before navigation:
when one first visits a page, it's nice to have all the doors to all the different parts of the site immediately available. The reason older homes used to start you right out with a foray (is that what it's called? A big room/hallway you walk into) with several different doors going to different parts of the house.
This makes sense for simple, small, main-site navigation, not something like a 100-link-long products list.
I put content first, then breadcrumbs, then section navigation, then top nav, then footer.
Only on the homepage I change the order a bit: top nav, content, footer.
Don't need to change the CSS for it, body has a top padding & headnav is placed absolute (it's always a fixed height).
I do have a lot of links (at least 3-4) in the content, that lead to deeper pages on the linked subject.
& Every navigation gets a title, even the breadcrumbs. I do hide those titles in the design. (display none.)
page structure looks like this on a deep page:
Code:
<body>
<div id="container">
<div id="content">
<h1>page title</h1>
<p>content content content</h1>
</div
<div id="breadcrumbs">
<h2>Breadcrumbs</h2>
<ul><li><a /></li></ul>
</div>
<div id="section_nav">
<h2>Section navigation</h2>
<ul><li><a /></li></ul>
</div>
</div>
<div id="header">
<h2>website tagline</h2>
<h2>Head navigation</h2>
<ul><li><a /></li></ul> (first link is home with logo)
<h2>Second navigation (mostly sitemap, contact, etc ...)</h2>
<ul><li><a /></li></ul>
<h2>Language navigation</h2>
<ul><li><a>this page in another language</a></li></ul>
</div>
<div id="footer">
<h2>Footer navigation</h2>
<ul><li><a /></li></ul>
<h2>copyrights</h2>
<p>copyright</p>
</div>
</body>
Dan Schulz you will be missed 
Bookmarks