• entries
383
1075
• views
352190

# trazoi.net - fresh new looks

106 views

I've put in my first alpha version of the new skin for my site at trazoi.net. I'd be grateful if you could go check it out and tell me what you think.

There's some known issues, the biggest being a glitch with the nav bar in Internet Explorer; the header for the site overlaps it for some reason. I only caught this when doing some last minute compatibility checks before uploading the new CSS, but since it's still usable in IE and appears to work fine in Firefox, Opera and Safari I thought it was worth uploading for a day. I'll see if I can fix that problem tomorrow (well, technically later today). It's too early in the morning to dig into obscure CSS and PHP issues right now.

Thanks for any feedback, and once again, the site's at trazoi.net (not at the journal subdirectory anymore; it's moved).

chocolicious

Hey, welcome to the world of web development IE headaches! One thing that I recommend doing right away is making a CSS reset template so that you can remove the default rendering across all browsers so that they'll all look the same when you start applying your own CSS.


html, body, div, span, applet, object, iframe,
h1, h2, h3, h4, h5, h6, p, blockquote, pre,
a, abbr, acronym, address, big, cite, code,
del, dfn, em, font, img, ins, kbd, q, s, samp,
small, strike, strong, sub, sup, tt, var,
dl, dt, dd, ol, ul, li,
fieldset, form, label, legend,
table, caption, tbody, tfoot, thead, tr, th, td {
margin: 0;
border: 0;
outline: 0;
font-weight: inherit;
font-style: inherit;
font-size: 100%;
font-family: inherit;
vertical-align: baseline;
}
/* remember to define focus styles! */
:focus {
outline: 0;
}
body {
line-height: 1;
color: black;
background: white;
}
ol, ul {
list-style: none;
}
/* tables still need 'cellspacing="0"' in the markup */
table {
border-collapse: separate;
border-spacing: 0;
}
caption, th, td {
text-align: left;
font-weight: normal;
}
blockquote:before, blockquote:after,
q:before, q:after {
content: "";
}
blockquote, q {
quotes: "" "";
}


What I typically do is start a new css with this template and then remove and alter as I modify my theme.

Quote:
 Original post by Mayan Obsidian Hey, welcome to the world of web development IE headaches! One thing that I recommend doing right away is making a CSS reset template so that you can remove the default rendering across all browsers so that they'll all look the same when you start applying your own CSS.

Thanks - I'll give that a go. my CSS is a bit complex because it's acting as a mod for the default WordPress theme, using the "cascading" nature of CSS, however this means that it's tricky to know exactly where a property is being defined. I'll probably forgotten to overload one of those properties you've listed.