The most recent blueprint release seems to emphasize its ability to easily customize column and overall website widths without having to re-create the whole framework.
At http://www.jdclayton.com/blueprints_compress_a_walkthrough.html , Joshua Clayton says:
One of the purposes of the revamping of the Blueprint scripts was to eliminate the need for a lot of the other websites out there that help you build custom grids, semantic namespaces, etc.
To do this the blueprint code now comes with a simple ruby script that lets you customize your number of columns, width of column, and width of gutter, among other things. However, it isn't easy to use the custom generated css files that this script creates with this drupal blueprint theme. The standard blueprint 24 column layout is hard coded into some of the functions that create things like the body class and subsequent areas of the website.
I am interested in developing some flexibility in these functions to allow for these custom blueprint layouts. I don't want to go to far down that path though unless this type of contribution would be welcome in the theme. I wonder if the core intention for this theme is to be a base drupal theme with lots of very useful theme tricks, or a blueprint css framework wrapper for drupal. I sorta hope it can be both.
Thanks for any thoughts.
Comments
Comment #1
bryan kennedy commentedAfter doing some experimenting I realized that it would have been better to ask this as more of a support question.
If I am using custom blueprint layouts what is the best way to go about implementing them. I suspect the answer is, modify the span-# entries in the template.php file.
But do we want to make this easier for the average user. Maybe the answer isn't new code, but some explanatory text about this process in the readme.txt section USING BLUEPRINT.
Comment #2
designerbrent commentedI would say there is a couple different approaches to doing this. The easiest is to is to go in and modify the template.php files to output the proper numbered span-# class name. That is what I currently doing every time I use it and need it different then it ships.
Second, we could create a setting on the settings page to change the width of the columns.
Third would be to implement the blueprint Ruby script in php somehow so that it can easily be customized. This would be really cool, but I don't know if the theming system can be pushed that far on it's own. Do you have to create a custom module that goes with the theme? Is it really worth that much hassle to install a module to edit a theme?
Comment #3
designerbrent commentedComment #4
designerbrent commentedAdding this to the dream list.
Comment #5
designerbrent commentedIntegration with the Skinr module would probably be a good approach for this.
Comment #6
zdean commentedsubscribe