Hi, the beauty of blueprint is that there's really no magic involved. You get:
* A good reset
* Attractive typographical defaults
* Some simple formatting classes
* A grid
So if I were creating a complex layout and the header portion of the
page would be difficult to do with the grid then I'd just not use the
grid for that part of the page. For example, create one 24 column box
for all of the header elements and put your primary and secondary
links and branding into it and style it the way you would on a normal
blueprint site. Then use the grid elements below.
It's not like Ruby on Rails or similar types of frameworks where you
start to lose the benefits of the framework when you break away from
the conventions. This is probably because of CSS's cascading nature.
Just take the parts you want and use them how and where you want.
--
Matthew Nuzum
newz2000 on freenode, skype, linkedin and twitter
> For example, create one 24 column box
> for all of the header elements and put your primary and secondary
> links and branding into it and style it the way you would on a normal
> blueprint site.
I meant, "style it the way you would a normal non-blueprint site"