http://www.xeroseven.net is the splash page where yes I used nodethirtythrees CSS as a guideline, as I don't know much about CSS atm but I plan on changing the positioning on this.
http://www.xeroseven.net/main.htm is the website itself
http://www.xeroseven.net/default.css is the CSS for it
I made all of the images on the website in photoshop myself. Feel free to say whatever you wan't.
/*
Stealing is wrong. -Xeroseven.net
*/
lol
Anyway. Sometimes you can have too much structure, for example right in your header you have:
<#header>
<#menu>
<ul>
When really, since a <ul> is a block-level element, and inherently a wrapper in the first place, you don't necessarily need <#menu> unless you anticipate some non-list-item existing in that space...
Then, you have empty elements like <#xbgA> and <.divider>, which are likely only there for presentational reasons and not structural ones. These can likely be obviated by using more well-planned CSS in future projects.
There are other places where you seem to be using more structure than is needed, or classing things that don't necessarily need to be classed (like all your <span.date> in <td.first>, where the date is already the only content there; why not class the <td> as .date in the first place--unless I'm missing something?), or having weird document trees, that give you results like: <#inner><#main><#main_inner>, etc. Also, with so many apparently disparate things classed <.content>, it makes me intuitively think perhaps you should just define whatever you're attributing to it more globally (like to <p> for example, although I haven't really scoured your code; this is all just from a quick glance at things)...
