Inger Eik wrote:
Well, I've made some adjustments to the attached files. Just be aware that when I downloaded the bits and pieces of your site to my desktop, I saved it all on the same level, therefore you'll have to correct the paths to css files and images.
I am studying the files to understand what was done:
In the top portion of the css2.css file where you have:
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, img, ins, kbd, q, s, samp,
small, strike, strong, sub, sup, tt, var,
b, u, i, center,
dl, dt, dd, ol, ul, li,
fieldset, form, label, legend,
table, caption, tbody, tfoot, thead, tr, th, td,
article, aside, canvas, details, embed,
figure, figcaption, footer, header, hgroup,
menu, nav, output, ruby, section, summary,
time, mark, audio, video {
margin: 0;
padding: 0;
border: 0;
font-size: 100%;
font: inherit;
}
I'm assuming you are just assigning these values (margin, padding, etc.) to all the tags above it?
So, can that and the one right below it:
/* HTML5 display-role reset for older browsers */
article, aside, details, figcaption, figure,
footer, header, hgroup, menu, nav, section {
display: block;
}
be used in most CSS files for websites, at least as a starting point?
Then, there are 2 body tags (not sure if you did that on purpose or not);
the first being:
body {
line-height: 1;
}
and then roughly 30 lines under that:
body {
}
Also, I see you put the entire header tag in the HTML above the container tag . . . what advantage/disadvantage is that, or is that just preference?
Thank you very much!
-- me