Velocio, can I make a couple of suggestions that will make the code leaner.
-itis seems to have taken hold, only with the tag. A section should group logically related items. You're using it on the home page just as a general delineator with a single item in each section:
[code]
Forums GeneralRides & RacesUKFGSS
[/code]
I would use a UL to organise that^ list. Because it's a list.
Now if you have read this: http://blog.whatwg.org/is-not-just-a-semantic
you may have decided that this is exactly what you want, so ignore me.
If not, then using a list for the forum list will save you lots of bytes, and continuing to use
where you don't want to attach semantic meaning (but just need a layout container) will save you 8 per tag pair.
This code makes the section title "belong" to the nav, and by losing the anonymity and putting it in
tags gives you the ability to write CSS that only applies to the heading, not the list as well. Obviously you can change the H2 to whatever block level tag (p, div, h1, h3 etc) you feel more appropriate.
you can use the clearfix class on the nav element to get rid of the br as well (which should not really be used outside a paragraph or table cell)
I also noticed a rule
[code]
.one {
display: block;
float: left;
margin-left: 0px;
width: 20%;
}
[/code]
When you float an element you make it block level so you can lose the "display:block". (By contrast to avoid the IE6 double margin float bug you can put display:inline after the float which will be correctly ignored by all browsers but will suppress the bug.)
You're using HR tags all over the place to get dashed and solid lines. They are unnecessary and can be replaced by putting border styles on the boxes.
I'm intrigued by this at the bottom taking up a lot of space with all that inline CSS to do nothing:
[code]
[/code]
Oh, one last thing: you;re using
a lot which is cool, but does it have any advantages over using
etc? It's costing you 8 bytes per tag pair. should wrap a whole section, as with or
Shit, I really should start a blog or write a book about this sort of stuff.
Velocio, can I make a couple of suggestions that will make the code leaner.
[code]
Forums
[/code]
I would use a UL to organise that^ list. Because it's a list.
Now if you have read this:
http://blog.whatwg.org/is-not-just-a-semantic
you may have decided that this is exactly what you want, so ignore me.
If not, then using a list for the forum list will save you lots of bytes, and continuing to use
i.e. for each nav list:
[code]
[/code]
You should be able to style just the navs and lose the rest: e.g.:
[code]
footer nav {
}
[/code]
[code]
[/code]
This code makes the section title "belong" to the nav, and by losing the anonymity and putting it in
tags gives you the ability to write CSS that only applies to the heading, not the list as well. Obviously you can change the H2 to whatever block level tag (p, div, h1, h3 etc) you feel more appropriate.
you can use the clearfix class on the nav element to get rid of the br as well (which should not really be used outside a paragraph or table cell)
I also noticed a rule
[code]
.one {
display: block;
float: left;
margin-left: 0px;
width: 20%;
}
[/code]
When you float an element you make it block level so you can lose the "display:block". (By contrast to avoid the IE6 double margin float bug you can put display:inline after the float which will be correctly ignored by all browsers but will suppress the bug.)
You're using HR tags all over the place to get dashed and solid lines. They are unnecessary and can be replaced by putting border styles on the boxes.
I'm intrigued by this at the bottom taking up a lot of space with all that inline CSS to do nothing:
[code]
[/code]
Oh, one last thing: you;re using
a lot which is cool, but does it have any advantages over usingetc? It's costing you 8 bytes per tag pair. should wrap a whole section, as with or
Shit, I really should start a blog or write a book about this sort of stuff.