<?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: Brave New World WordPress theme</title>
	<atom:link href="http://www.thatstandardsguy.co.uk/2009/04/brave-new-world-wordpress-theme/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.thatstandardsguy.co.uk/2009/04/brave-new-world-wordpress-theme/</link>
	<description>a web developer with standards</description>
	<lastBuildDate>Sun, 24 Jan 2010 17:34:11 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Peter Mah</title>
		<link>http://www.thatstandardsguy.co.uk/2009/04/brave-new-world-wordpress-theme/comment-page-1/#comment-1302</link>
		<dc:creator>Peter Mah</dc:creator>
		<pubDate>Sun, 24 Jan 2010 17:34:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.thatstandardsguy.co.uk/?p=296#comment-1302</guid>
		<description>Thanks very much for the theme. It was easy to implement with everything stripped out but the basics. And it&#039;s a great way to get your feet wet with HTML5.</description>
		<content:encoded><![CDATA[<p>Thanks very much for the theme. It was easy to implement with everything stripped out but the basics. And it&#8217;s a great way to get your feet wet with HTML5.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris Pratt</title>
		<link>http://www.thatstandardsguy.co.uk/2009/04/brave-new-world-wordpress-theme/comment-page-1/#comment-1301</link>
		<dc:creator>Chris Pratt</dc:creator>
		<pubDate>Sun, 24 Jan 2010 08:02:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.thatstandardsguy.co.uk/?p=296#comment-1301</guid>
		<description>@Micah: Technically, in HTML5 its perfectly valid to have multiple H1 elements. HTML5 utilizes a context-sensitive outline, where each header, footer, section, aside, etc. can each use H1-H6 and the headings are weighted against each other by their parent&#039;s position in the outline.

The equivocation of H1 to &quot;page title&quot; is really a bastardization of the spec for the purposes of SEO and aiding assistive devices. HTML5 provides better (and actual) hooks. It&#039;s fine to have multiple H1&#039;s because the search bot or screen reader will know that the H1 in the header element is of greater value than an H1 in an aside element, etc.

That said, this all hinges on support for HTML5 in these devices, which obviously is anything but guaranteed at this point. As a result, it is probably still best to have only one H1 at this time.</description>
		<content:encoded><![CDATA[<p>@Micah: Technically, in HTML5 its perfectly valid to have multiple H1 elements. HTML5 utilizes a context-sensitive outline, where each header, footer, section, aside, etc. can each use H1-H6 and the headings are weighted against each other by their parent&#8217;s position in the outline.</p>
<p>The equivocation of H1 to &#8220;page title&#8221; is really a bastardization of the spec for the purposes of SEO and aiding assistive devices. HTML5 provides better (and actual) hooks. It&#8217;s fine to have multiple H1&#8217;s because the search bot or screen reader will know that the H1 in the header element is of greater value than an H1 in an aside element, etc.</p>
<p>That said, this all hinges on support for HTML5 in these devices, which obviously is anything but guaranteed at this point. As a result, it is probably still best to have only one H1 at this time.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Karl Dawson</title>
		<link>http://www.thatstandardsguy.co.uk/2009/04/brave-new-world-wordpress-theme/comment-page-1/#comment-1299</link>
		<dc:creator>Karl Dawson</dc:creator>
		<pubDate>Fri, 18 Dec 2009 08:24:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.thatstandardsguy.co.uk/?p=296#comment-1299</guid>
		<description>Hi Micah, thanks for the feedback - that&#039;s a good idea, I&#039;ll have to look into it!</description>
		<content:encoded><![CDATA[<p>Hi Micah, thanks for the feedback &#8211; that&#8217;s a good idea, I&#8217;ll have to look into it!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Micah</title>
		<link>http://www.thatstandardsguy.co.uk/2009/04/brave-new-world-wordpress-theme/comment-page-1/#comment-1298</link>
		<dc:creator>Micah</dc:creator>
		<pubDate>Fri, 18 Dec 2009 05:34:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.thatstandardsguy.co.uk/?p=296#comment-1298</guid>
		<description>Awesome! Very cool HTML5 theme for Wordpress. A copule of comments:

This validates as XHTML5, which I prefer anyway since you have self-closing tags for elements like meta and link. Mostly just an FYI.

Once you get into any Post, you&#039;ll notice in the markup that there are two H1 tag sets, one for the logo/site name and one for the Post title. No matter your preference, there shouldn&#039;t be two H1 tags in the document! 

I think the best markup replacement for this is to have an if statement on the H1 in the header tag so that if it&#039;s not the front page this tag becomes a div or paragraph with an ID property.

I think the H1 tag should always be the page&#039;s description, and when you leave the homepage, the logo or site name becomes secondary to the Post or Page title. Thus, the H1 should change ownership.

Just thought I&#039;d throw this out there. Thanks so much for providing this!</description>
		<content:encoded><![CDATA[<p>Awesome! Very cool HTML5 theme for Wordpress. A copule of comments:</p>
<p>This validates as XHTML5, which I prefer anyway since you have self-closing tags for elements like meta and link. Mostly just an FYI.</p>
<p>Once you get into any Post, you&#8217;ll notice in the markup that there are two H1 tag sets, one for the logo/site name and one for the Post title. No matter your preference, there shouldn&#8217;t be two H1 tags in the document! </p>
<p>I think the best markup replacement for this is to have an if statement on the H1 in the header tag so that if it&#8217;s not the front page this tag becomes a div or paragraph with an ID property.</p>
<p>I think the H1 tag should always be the page&#8217;s description, and when you leave the homepage, the logo or site name becomes secondary to the Post or Page title. Thus, the H1 should change ownership.</p>
<p>Just thought I&#8217;d throw this out there. Thanks so much for providing this!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Remy Sharp</title>
		<link>http://www.thatstandardsguy.co.uk/2009/04/brave-new-world-wordpress-theme/comment-page-1/#comment-1215</link>
		<dc:creator>Remy Sharp</dc:creator>
		<pubDate>Tue, 07 Jul 2009 16:31:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.thatstandardsguy.co.uk/?p=296#comment-1215</guid>
		<description>Hi Karl,

Can I suggest you change from using a static html5.js (the one included in the JS directory) to hot linking the version I&#039;ve just today pushed up to Google code.

The reason for doing so means it will automatically benefit from additional elements (for example the copy of html5.js is missing the hgroup element - no that I can ever image using it).

It&#039;s being served with the right mime type, so it shouldn&#039;t cause you any problems:

http://html5shiv.googlecode.com/svn/trunk/html5.js

Cheers,

Remy.</description>
		<content:encoded><![CDATA[<p>Hi Karl,</p>
<p>Can I suggest you change from using a static html5.js (the one included in the JS directory) to hot linking the version I&#8217;ve just today pushed up to Google code.</p>
<p>The reason for doing so means it will automatically benefit from additional elements (for example the copy of html5.js is missing the hgroup element &#8211; no that I can ever image using it).</p>
<p>It&#8217;s being served with the right mime type, so it shouldn&#8217;t cause you any problems:</p>
<p><a href="http://html5shiv.googlecode.com/svn/trunk/html5.js" rel="nofollow">http://html5shiv.googlecode.com/svn/trunk/html5.js</a></p>
<p>Cheers,</p>
<p>Remy.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
