Is this one of the big lessons, at least in my project which folks have been helping me with?

The lesson being: establish your main divs, then achieve specific variation through classes?

Sorry if it seems like a dumb question...

Not dumb at all, but rephrase it to something like...

"Establish your main source-code *elements*, then achieve specific style-variations through *ID*s and *classes* and good use of the *CSS cascade*."

...and you'll be on the right track.

What I mean is: <div>s are generic block-level elements with no inherent visual styling, used primarily for grouping elements into <division>s where use of more specific block-level elements doesn't make sense. A browser generation or so ago we sometimes had to add extra <div>s so we could style our pages/documents the way we wanted across browserland. Today we can in most cases limit the use of <div>s to "what's absolutely necessary for meaningful <division>s and no more", and in the future we will be able to rely on slightly more specific and better (more meaningfully) named versions of the humble <div> - HTML5 specs - to make our source-code a bit more meaningful and easier to target through the cascade for overall and specific styling.

regards
        Georg
______________________________________________________________________
css-discuss [[email protected]]
http://www.css-discuss.org/mailman/listinfo/css-d
List wiki/FAQ -- http://css-discuss.incutio.com/
List policies -- http://css-discuss.org/policies.html
Supported by evolt.org -- http://www.evolt.org/help_support_evolt/

Reply via email to