Reading information like this, regardless of whether it is 100% correct or not, is like gold. I wish more blogs would attempt to comment on things such as these, even when they know their implementations could be incorrect. It’s how we all learn and people will be able to solve these problems out quicker.

I hope I can read another HTML5 post soon.

Although maybe this is a good use case to put to the whatwg for why h tags *should* be allowed in footers?

I’m of the opinion that H(n) should stay out of the footer, the only information that should go in there is stuff that complies with the companies act like company registration number, email and street address, vat number and telephone number etc.

By all means, stick in a section element/div tag if you want to make another section above, pretending it’s still part of the footer. However this is something which again could be debated all day, there’s no right or wrong answer.

On a side note, I’ve got something which I’ll be sending to you in an email this week. It could be quite handy.

Using the body for my wrapper is a stroke of genius but then again I don’t expect anything less from you now

With regards to the whole of your third paragraph it’s on the money. When I was building the site I thought I was using the correct elements but now that I’ve read more into the spec I can see that some of the areas you’ve highlighted could be with reworking.

That’s the problem with the spec currently, there’s just too much scope in there. We need a list. It doesn’t need to cover every element, just the main ones highlighting a few things that it can and cannot be used for.

I’m very much looking forward to see your site when you push it live.

I had a play about with your site in Firebug the other day and found a way to drop that wrapper div. The body tag should be used as your wrapper

I disagree with your use of asides on your entry pages, and also your use of an aside within an aside. On entry pages, your “post details” aside would be better suited to a footer as part of the article, then the next column could be an aside. On your articles page, you could wrap both columns 2 and 3 in an aside but beneath that they should be sections since they are both the same “aside” (filtering options) but have their own specific grouping (type of filtering).

Whether or not an aside is appropriate for sidebar content is endlessly debatable! I believe it should only be used for things like related links, trackbacks and pull-quotes. Site-wide sidebars listing projects should be in a section. However, if you were on a project page then a list of more projects would be in an aside. I hope this makes sense!

Very nice write-up though, I will do the same once I finish my transition.

Although maybe this is a good use case to put to the whatwg for why h tags *should* be allowed in footers?

Good to hear from you! As we all know working with this spec is more an experiment than anything else right now.

The article problem posed alot of problems. Infact, if I’m to tell the truth I’ve been a bit sneaky about it. On my index page I’ve wrapped my articles, as you have pointed out in a section tag. However if you go to my articles page, second link on the main nav, you will see I’ve wrapped my articles in an article tag. I’m still currently trying to find the best method and seeing if browser/google interpret these pages differently.

As for hGroup, totally agree, I’m steering clear for now.

Cheers mate. Any questions give me a shout, my answers won’t be perfect by any means but at least they’ll be “along the right lines”

@msikma

Thank you, although I think I’ll leave that challenge to someone else haha.

@Rich

Nice tip about the H1s. I had never thought of actualling doing that, I’ll be looking into later this evening. It could prove to be very handy.

Regarding the H3s, when I was creating the site the validator threw up lots of errors because I had incorporated H(n) in my footer. Is this no longer the case?

Although, if errors were still to occur I guess I could always move that section outwith the footer.

I was going to put my main logo/header in a hgroup but it seems a bit pointless having a hgroup element with only one header in. Hgroup is brandspanking new though so I’m sure it will change.

I love how using html5 we can get away from using loads of div tags, however I find I am adding more tags now such as putting more things in headers or footers, things like that.