So this is my pro/con list of the blueprint framework that mark bolton used for the prototyping of the new drupal.org
First up: Im a big fan of finding a unified way of doing the frontend work, but im not in it for any course - a frame work isnt good task B just because somebody else uses it for tast C.
Mark Boulton uses blueprint for their prototyping, which makes a lot of sence. Theres a lot predefined classes that makes it really easy to quickly build up a bunch of pages in html.
In prototyping its not the beauty of the mark up code thats the point, its the functionality of the pages, and getting everything sketches out with the client. (and btw is a huge help for the theming planning)
So know that we are at the point where we have to theme this beautiful design, the argument were made in cologne that we should just use the prototypes that Mark Boulton (MB) already had done, so we could be faster on our way to get the design implemented.
I know it makes sense to just use what somebody else already has done, but people this is our new home! we should go for the best possible frontend we possible can get, and remember one of the lessons that we have learned the last couple of years. - The theme should not be on 1 man/woman's shoulders.
We should NOT use the blueprint based markup & style that MB has created for the protostypes because:
Blueprint basically sets up a ton of region sizes, and by looking at the designs we need 4-6 basic widths - so to load 200+ classes would be total overkill - we have more than enough classes in a drupal site as it is, and we dont need to confuse the themers more.
Bloat is not only the 4-5k's of stuff we load to the end user, its also the ton of css files & classes that the themer has to know there is
Non semantical naming - its more or less impossible to read the code and figure out what is what in the markup.
Blueprint is not build to put the content first :/
yeah lynx still rocks, and the accessibility people are gonna love us, not to say the seo freaks.
The blueprint framework (and others) builds on the idea of adding classes to every piece of markup that needs a width
div class="grid-14"> Theres a lot of places in drupal thats not so easy to get a hold of and add a class to that specific markup, so we will end up at one time or another with width settings in the .css files, and again make it less obvious for the next themer to figure out whats going on.
Speed - i Guess the Gerhard & the server guys would be happy if we didnt end up with a ton of markup that every visiter on the sites ends up downloading?
Theres no reason to make a quick & dirty solution thats gonna haunt us the next 4 years.
lets find the right way todo this, and yes we will have a version to show the drupallers in DC
As i see it MB really build it on the 960 grid system, that a couple of themers are working on now to get into d7 (), and they only used the 24 grids based blueprint as a prototyping tool (so at this point i have som questions to the prototypes, where it dosnt follow the 20px gutter, but only have a 10)
..."Please note: These prototype files are to indicate and demonstrate functionality only. They are not indicative of the final design of the website."
- This is the drupal site! - we should go for perfection and not just a quick solution!
I really cant se any good reasons for jumping on the blueprintCSS framework - unless were cutting it down to a bare minimum and change the way the grid is set up.
What we should do IMHO:
Set up hte basic css& markup rules:
blueprint & 960.gs both framworks have really got stuff, more or less the same - no surprise there.
MB has already set up the rules, so were gonna code them into place i really think we should calculate them to use 'ems instead (http://www.alistapart.com/articles/howtosizetextincss) but thats a minor geeky detail
The basic pages are all using 2,3,4 & 5 colums , these are based on the 960 so we gonna reuse som of the the width definition, and the aplha / omega
(btw 960 in drupal -> http://groups.drupal.org/node/16457) - so here we can cut out all the crap and just work with the basics
*Define classes & regions so they make sence for us all (and in a year)
header footer, left bar, menu etc you know the drill?
In the next couple of days im gonna sketch up the classes & markup that can provide us with the setup that we need, unless somebody is gonna oppose on this?
or have a really good reason to why we should use blueprint for all our css needs