Excellent question. As blueprint ships, that is certainly an issue. However, that is what the compress.rb script is for.
Per the link that follows, you can set it up to create semantic classes or id's like .sidebar, .content, .header, etc, that actually have the same rules as .span-6, .span-12, .span-24, etc. The compress script really makes it very flexible and useful for those that don't want the presentation and content mixed. http://www.jdclayton.com/blueprints_compress_a_walkthrough.html Hope that helps. - Brent --------------------------------------------------------- Design / Interaction / Strategy http://brenthardinge.net --------------------------------------------------------- On Thu, Dec 4, 2008 at 7:26 AM, Blueprint Newbie <[EMAIL PROTECTED]> wrote: > > Maybe this has come up before, but doesn't the span-x approach push > presentation information back into the content? (by explicitly naming > a number of columns). > > It would be nice if I could have my layout divs' styles be defined as > a composition of blueprint classes in my stylesheet. AFAIK this is not > possible with CSS - it would require OO-style inheritance. For > example, it would be nice to do this: > > #header extends span-24 { } > #left-sidebar extends span-4 { } > #main-content extends span-16 { > background-color: white; > } > #right-sidebar extends span-4 last { } > > Are there other ways to do this that would allow us to use blueprint's > grid support, yet keep the "x" in "span-x" out of our HTML? > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Blueprint CSS" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/blueprintcss?hl=en -~----------~----~----~----~------~----~------~--~---
