Try Tuts+ Premium, Get Cash Back!

Which CSS Grid Framework Should You Use for Web Design?

Tutorial Details
  • Difficulty: Beginner

Ever wondered how all those slick “magazine” themes for WordPress and other platforms were created? Many, if not all, were designed using a CSS Grid Framework – at least in essence if not in actual fact. That is, you can use an existing CSS framework or build your own from scratch. While it’s possible to design complex web page layouts without a framework, it’s arguably an act in masochism. In this article you’ll get an overview of the current batch of Frameworks and which you should choose to use.

What is a CSS Grid Framework?

Layout grids have been used in print publishing long before the Web. They’re an invisible foundation used to achieve visual cohesion in magazine and newspaper page design and layout. They essentially amount to a lattice that divides horizontal and vertical space in consistent units where text, headlines, images, and advertising can be placed.

The same concept has been adapted for web page design for much the same reason, using CSS (Cascading StyleSheets) code to position HTML elements. In fact, many editorial sites run by large print media publishers do apply grids to achieve a look on their websites that’s similar to their print content.
Note that the vertical axis is not as well supported in CSS Grid systems, since a web page’s height is not as much of an issue as for a printed page. (Still, that’s a minor issue in web page design, unless you expect the same features as with Desktop Publishing – aka DTP – systems, which is difficult to support without a PostScript-like language for browsers to implement and support.)


960 CSS Grid System – one of the nicer designs for a framework website :-)

Why Use a CSS Grid Framework?

Not all designers support the use of using grid frameworks over tables, or even at all. But let’s face it; there are layouts you simply can’t do with just HTML tables without a great deal of painful effort – and lots of nesting that’s hard to decipher, should ever have to make changes.

Sure, if you use grids, you’ll have to add some necessary HTML tag markup to your content, thus increasing page file sizes. Also, this means that markup and style are not truly separated – a tenet which many web designers would like to adhere to. (Some people feel, rightly or wrongly, that naysayers of CSS frameworks are designers who are worried that the need for their services will decline. Though, with this logic, coders are in trouble, too, especially with the increase in cross-browser code libraries such as jQuery.)

The fact is, using a CSS grid framework means that your browser loads the CSS file(s) only once and keeps them cached “on the client side”. Plus, the additional HTML markup needed to apply the “invisible” CSS framework is rarely so significant that bandwidth issues for readers should be a concern. (Interestingly, most of the naysayers seem to be talking about Yahoo UI Grids, not so much Blueprint.)

In most of the examples I’ve been working with, and in any of the magazine themes using grids that I’ve inspected, we’re talking relatively small file size increases – especially compared to the blog platform code being used. A single large image will likely take up more space. With faster Internet connections, it really isn’t such a big deal.

Design & Aesthetic Benefits

Regardless, of whether you use CSS grids for prototyping or production systems, there are multiple aesthetic and design benefits:

  1. Visual design cohesion between page elements.
  2. Uniformity and consistency in HTML element placement, thereby reducing CSS coding errors.
  3. Easier to apply the “rule of thirds” and the “golden section” to design, which results in a visually appealing layout to most human eyes.
  4. Mostly eliminates the need to use nested HTML tables.
  5. Nested sub-grids, for very complex designs that are relatively simple to produce.
  6. Easier to apply images and text callouts to produce asymmetric layouts for visual texture.
  7. Cross-browser support, so less screaming and hair pulling when you get around to testing for that bane of designers, IE. (Bill Gates must have felt so unloved as a child to have produced so much software that does what it wants, in defiance of standards that MSFT supposedly supports.)
  8. Reduced effort for producing slicker web page layouts, compared to coding the necessary CSS from scratch.
  9. Reduced future effort if you need to reposition elements or change rendering characteristics (typography, margins, etc.) for related elements en masse.
  10. Usable with static pages and CMSes/ blog platforms.
  11. Enables the popular use of creating “magazine” and premium themes for blog platforms. (WordPress seems to be the platform that CSS frameworks are most often used with, though any other platform that allows referencing a JavaScript source file should work just fine.)

YAML – “Yet Another Multicolumn Layout”

CSS Frameworks and Tools

Here’s a short list of some of the more popular frameworks:

  1. Blueprint CSS Grid Framework.
    Robust despite only being in V0.7 (as of this writing), with lots of support from designers, and numerous tools for generating CSS code (beyond the standard 24-column, 950 px default framework). Supports the use of Blueprint “plugins”.
  2. Yahoo! YUI Grids CSS, Grids Builder.
    This framework, which predates Blueprint, comes with six preset templates and four preset widths, and the layouts accomodate IAB ad unit guidelines. YUI Grids CSS is integrated with the rest of the Yahoo! UI (User Interface) Library.
  3. YAML, YAML Builder.
    YAML (Yet Another Multicolumn Layout) has a fair bit of maturity, is built on web standards, and is supposedly easy to use. Though it doesn’t seem to have all that much use in the WordPress community. In fact, in the many hundreds of WP themes I’ve looked at for the last three years, I don’t recalling seeing it used once. That might be because you need a license to use it with some CMSes (Content Management Systems).
  4. Grid Designer.
    This is a web tool for generating custom CSS grids. It uses its own CSS classes, so it could be said to be a framework, though it’s not as well support in the design community as some of the others.
  5. 960 CSS Grid System. This system is based on a page width of 960 pixels, which is a number that’s divisible by many other numbers, making it “a highly flexible base number to work with.” However, 960 Grid only works with 12 or 16 columns.
  6. CSS Boilerplate. Produced as a stripped down framework by one of the original Blueprint authors.
  7. Sparkl. The documentations says you can create 1-, 2-, or 3-column pages, but the samples suggest you have more flexibility.

There are other CSS Grid frameworks you can find listed in Google Code, but of the three or four more that I looked at, most were incomplete in terms of documentation or even project files, so I’ve left them off. If you know of a framework not listed, please do let us know in the comments!

Comparison

Let me point out that this is not a comphrensive comparison of CSS frameworks. In fact, I’ve not used anything extensively other than Blueprint, though I’ve scanned docs for all of the frameworks listed above and played a bit with YAML and Grid Designer. Blueprint, YUI Grids, and YAML are arguably the "big three" in the CSS framework space, and 960 seems to be a solid fourth choice.

In choosing a framework, I’ve taken into account that I’m not a trained designer – beyond what I’ve studied on my own for years. I do dabble in design when necessary, albeit in a very minimalist form. In fact, because I spent quite a few years either publishing my own print magazine or working on others, I did a fair bit of (really bad) page layout using the principles of grid design working with Adobe PageMaker. So I find it very natural to work with CSS Grids for web design. It seems that given the number of WordPress themes out there – see the list at end of this article – that are based on a grid framework (mostly Blueprint), designers feel pretty comfortable with grids, too.

Nevertheless, with time always limited, I need something easy to learn and use, yet robust. I’ve found that Blueprint CSS Grid suits my needs. It integrates nicely with various JavaScript libraries – including jQuery, which can result in some damn sexy web interfaces. It renders well (though not 100% perfectly) in most browsers – though you need to test for that big thorn in web designers’ sides, IE browser.

Based on my loose research of CSS Grids this last year, Blueprint seems to be the most robust framework, the least restrictive, the most supported – in terms of how widespread its use is – the smallest in size, and the framework with the most tools. In fact, the beauty of Blueprint is that you can very quickly produce the CSS code for a custom framework using tools like Kematzy’s Blueprint Grid CSS Generator. Though you can do this with Grid Designer, a quick comparision would suggest it’s not as robust as Blueprint.

On the flipside, scanning and browsing the documentation for Yahoo! UI Grids CSS framework leads me to believe that if you just want to do some simple web page layout and want a handful of presets to play with, you might want to look into this option. However, I feel it’s a bit too restrictive for my liking. (You might want to read Foo Hack’s Blueprint CSS Framework vs YUI Grids.)

Ultimately, when it comes to learning something new online – such as a programming language and code library/ framework – I always apply the "shoulders of giants rule". I first shortlist the options that seem suited to what I need, then select based on how much it has been written about. Might not seem fair to newer options, but the process isn’t that much more arbitrary than how many people pick web applications to use. There’s too much out there to keep track, and having an existing supportive community makes a big difference.


Blueprint – My choice

Why I Picked Blueprint CSS

Blueprint CSS Grid Framework is what I’ll be using in all of my tutorials at NETTUTS (when it’s relevant). Instead of copying the feature list from the docs at Google Code, let me focus on why I personally picked it. Some of these points overlap with what I’ve said above:

  1. Relatively small file sizes. Has compressed versions for production use, for further size decreases.
  2. Print + screen stylesheets.
  3. Simple to integrate and use. (Though IE browsers are problematic, depending on which version of Blueprint is being used.)
  4. Easy to remember CSS classes and ids that are unlikely to clash with any that you’re already using.
  5. Lots of support tools, especially for generating custom grids.
  6. Lots of articles/ tutorials about Blueprint, with lots of positive vibe.
  7. Lots of use of Blueprint by WordPress theme designers.

As mentioned above, I do run into IE problems – but then doesn’t everyone? Several WP themes using Blueprint have resolved IE browser issues, so I’m extrapolating in my belief that they can mostly be resolved.
Blueprint, as of this writing, does not support liquid layouts – something I’m not a huge fan of anyway. However, such support is apparently coming, in case you lean that way.

Sample Grid-based Design Process

Well this is a matter of choice, isn’t it? Some CSS Grids come with a grid.png or even a .psd file that you can use in transparent mode in Photoshop, Fireworks, GIMP, etc., while you’re laying down your design elements. I’m a bit more old school and always design my layouts by starting on paper:

  1. Block off a bounding rectangle representing an entire web page. (Do this for each page you’re designing.)
  2. Partition the rectangle into smaller rectangles representing primary areas: header, footer, sidebar, content area, etc.
  3. Further partition primary areas and pencil in “atomic” design component (site, logo, rss button, recent posts, recent comments, search box, sample posts, post thumbnails, etc.)
  4. Translate that final sketch into skeleton HTML, using real text or lorem ipsum text. The HTML markup will include the necessary CSS Grid class and id values to support the layout I need.
  5. Create banners/ buttons in graphics software.
  6. Test HTML mockup in as many browsers and versions as possible. (You might need to employ a few friends if you only have one computer.)
  7. Convert text into CMS/platform code. (E.g., convert text blocks into the necessary WP function calls and PHP code.)

You’ll notice that nowhere in that process is the use of graphics software for layout mockup. That’s because I am not a designer and use a very minimalist approach for what I design (for myself only). But if you do plan to use, say, Fireworks for your mockup, you would do so between steps #3 and #4.

Summary

I’ve tried to be comprehensive in my search for CSS Grid Frameworks, scanning over 120 articles for leads. However, it’s possible I’ve missed some options, so feel free to offer others.
Whichever CSS framework you decide to use, do so because it best suits your general needs. If the pages/ templates you design will have advertising, consider what type of ads. Early on, when I picked themes for my sites, I chose for AdSense ads (which are IAB-compliant). More recently, I’ve been picking/ designing for blocks of 125×125 ads, which I highly prefer over most AdSense blocks.
If you’re interested, there is a W3C draft specification entitled CSS Grid Positioning Module Level 3 (written by two Microsoft employees) that discusses integrating grid-based layout into CSS. The features discussed in this draft could be in IE 8.

References

Related Tools

  1. Blueprint CSS AIR Grid Tool.
  2. Blueprint CSS Quick Reference (PDF, 1 page).
  3. CSS Grid Calculator.
  4. Diagnostic CSS.
  5. Reset CSS.

Some Articles or Sites About CSS Grid Frameworks

Here are links to a few of the many great articles out there about CSS Grids.

  1. 456 Berea Street – Grids, Tables, CSS.
  2. A List Apart – Thinking Outside the Grid, Setting Type on the Web to a Baseline Grid.
  3. Olav Bjørkøy – Launch: Blueprint, a CSS Framework.
  4. Mark Boulton’s 5-part series, Five Simple Steps to Designing Grid Systems.
  5. Jeff Croft – What’s Not to Love About CSS Frameworks?
  6. CSS Demos – Hands on With Blueprint, a CSS Framework.
  7. CSS Tricks – GridControl.
  8. Design by Grid.
  9. Cameron Moll – Gridding the 960.
  10. Smashing Magazine – Design With Grid-Based Approach, Six Creative Column Techniques.
  11. Stone Mind – First Impressions of the Blueprint CSS Framework.
  12. Subtraction – Oh Yeeaahh! (or How to Use Grid in a Layout)
  13. Tutorial Blog.
  14. Vandelay Design – 65 Resources for Grid-Based Design.
  15. W3 – CSS and Grid Layout.
  16. Web Designer Wall – Grid and Column Designs.

RevolutionThe Premium Theme

46 Free or Paid Specialty Themes

If you feel that you’re not ready to tackle grids and theme design yet but need a grid-based theme, here’s probably one of the most comprehensive lists you’ll find. (There are actually more than 46, if you include variations.) It includes magazine, magazine-like, gallery, specialty and various premium themes that use either explicit or implicit CSS grids. (It’s possible one or two do not use grids, though at first glance, they appear to.)
A few of these themes are free or have a free version. Most are for the WordPress platform. This list only includes themes available to the general public, not necessarily custom grid themes used by various bloggers. (See select links in the previous list, including Web Designer Wall and Smashing Magazine for snapshots of such sites. Also see Khoi Vinh’s Subtraction, as an example of a visually impactful grid-based site.)
Warning: Some of these themes might not work in WP 2.5x+

  1. Artfull Magazine. (Make sure you use the theme switcher on this page – bottom right corner.)
  2. Block Magazine.
  3. BranfordMagazine.
  4. Chimera Pro.
  5. Content Press.
  6. Cornerstone.
  7. CSS Gallery.
  8. Deadwood, Deadwood Lite.
  9. Fjords09.
  10. Forte. (Note: Currently showing a suspended page)
  11. Fresh News.
  12. Futurosity.
  13. Grid Focus.
  14. Gridline – Lite, News, Magazine.
  15. Gridlock.
  16. IndoMagz.
  17. Jello Wala Mello.
  18. Live Wire series.
  19. Magazine News.
  20. Massive News.
  21. Mimbo, Mimbo Pro.
  22. Monochrome – Gallery, Author, Pro, Lite.
  23. Nautica.
  24. News – Quommunication.
  25. NewsPixel.
  26. NewsPress.
  27. Options.
  28. Overstand.
  29. Premium News Theme – The Gazette Edition.
  30. Rebel Magazine.
  31. Revolution and several variations.
  32. Showcase Gallery.
  33. Simplicity.
  34. Structure.
  35. Tauren Pro.
  36. TMA – The Morning After.
  37. Trevilian Way.
  38. Victoria.
  39. Visionary.
  40. Visualization.
  41. WordPress Magazine (Gabfire).
  42. WP-Magazine Theme.
  43. WP-Polaroid.
  44. Ygo CMS.
  45. Your Revolution.
  46. Zeke.

The above list of magazine themes is compiled from the following references, as well as from searching Google.com.

  1. Bootstrapper.
  2. Clever Sage.
  3. Graph Paper Press.
  4. Michael Doig.
  5. The Blog Entrepreneur.
  6. Theme Playground.
  7. Vandelay Design.
  8. Visual Blast.
  9. Web Hosting Show.
  10. Squidoo Magazine Themes lens.

Note: Want to add some source code? Type <pre><code> before it and </code></pre> after it. Find out more
  • http://davidcarreira.com D. Carreira

    Nice article.

    David Carreira

  • http://www.refinedinternet.co.uk Michael Lomas

    I do find this article a little strange as well, as developers surely we can’t advocate the use of generic templates / frameworks?

    I’m all for re-usable code, where would we be without JS frameworks? But the use of XHTML frameworks seems to go against everything that’s generally accepted on the topic, no WYSIWYG editors, which is all they really are, we might as well make new sites using Dreamweaver’s pre-set layouts.

    However… I can see the bigger picture. When I create a new site there are always common features, certain stylesheet rules, the way I layout headers, footers and their ids/classes, in short, I have my own framework. Having a central resource for dealing with all cross browser issues that creates the common layouts isn’t necessarily a terrible thing.

    I think it comes down to preference, those not using public frameworks (like me) tend to have our own in house frameworks we stick to anyway. Those willing to accept a standardised approach should do so (and I’ll have a good look at them myself) as I’d bet it cuts a lot of time out of testing for browser errors.

    I think the key is understanding the code that you’re provided with, be it in house or framework based, so you’re in a position to manipulate it if required.

  • http://www.pieterc.be PieterC

    I don’t like the un-semantic name usage of most of this frameworks. The best you could use is CSS Boilerplate. Then you don’t get those ugly class names.

  • http://enhance.qd-creative.co.uk James

    I’ve never used a framework and I doubt I ever will…

    I honestly don’t see the advantage, most of them seem bloated and unecessary. I’m all for using reset stylesheets but I like to retain a sense of semantic logic within my HTML and CSS – a framework would “ruin” my workflow.

  • http://www.gomedia.us Jeff Finley

    Wow, this is an amazing resource. I never knew about CSS Grid Frameworks before now and those premium WordPress themes are a real gem. Thanks you guys.

  • James

    Fantastic list of resources!

  • Connor

    Nice Tutorial! One comment though…Speaking about the pain known as Internet Explorer, I just happen to be using it right now (1 in 1000 chance), and I notice the header (The spoonfed part) is mis-aligned by a pixel or so. I’m using IE7.

  • http://www.citizenpep.com Paul Palmer

    I think these grid frameworks are fantastic for those who are learning how to design and implement a grid-based site. Once you get used to them, you’ll find that it may be easier to roll your own to suit your personal taste/style. Also, as Sean pointed out, grid frameworks often suffer from “divitus” which is the snooty cousin of table-based design.

  • http://www.wbgufm.com Ryan

    Doing a major overhaul of our current site, this should be an immense help. I’ve heard of Blueprint in the past, however, never taken the time to learn about it. Thanks for the info!

  • Philm

    Alot of you who have posted above are mistakenly taking the “I’m too great to lower myself to use a CSS framework” or “Learn CSS and you won’t need one” approach. I think you’re all overthinking it and missing the point tbh.

    Maybe that’s the difference in attitudes between coders and designers, there’s no need to get all prickly about it. At the top of the article it says:

    “They’re an invisible foundation used to achieve visual cohesion in magazine and newspaper page design and layout. They essentially amount to a lattice that divides horizontal and vertical space in consistent units where text, headlines, images, and advertising can be placed.”

    Every magazine or printed piece of literature you read or see has been based on a grid of some sort, we don’t see publishers bickering saying “I’m not using a grid for my magazine, I’ll just throw stuff on the page because we can”.

    For traditional designers, taking a traditional approach online is a great idea and makes perfect sense…

  • http://www.showpage.it freddie

    Thanks for this article. I see the framework as a time saving. I’ll use it!

  • http://csswizardry.com/ Harry Roberts

    I’ve developed a framework solely for grid layouts and typography: http://csswizardry.com/typogridphy/

    Harry

  • http://www.freshclickmedia.com Shane

    Wow – a very good overview of grid systems – I’ve always found them to be a little bloated, but they’re very useful for a number of different applications and site designs, so thanks for posting the article.

  • http://www.rajdash.com/ Raj Dash

    Nettuts readers are without a doubt some of the nicest, most polite commenters I have ever read online. Even those that disagree are so polite. It’s been a joy to read all your comments, learning about all different points of view. Apologies that I haven’t really responded much to most. Thanks also for the links to all the examples and tools.

    cheers
    -raj

  • http://blog.highresolution.info djesse

    “Though it doesn’t seem to have all that much use in the WordPress community. In fact, in the many hundreds of WP themes I’ve looked at for the last three years, I don’t recalling seeing it used once.”

    This isn’t really an argument to describe the quality of YAML as a CSS framework. A more deep feature review would have been a good idea.

    “That might be because you need a license to use it with some CMSes (Content Management Systems).”

    This is completely wrong. YAML can be used free under Creative Commons License with every CMS you like.

    Best regards
    Dirk

    • Brian

      you do need a license if using for commercial purposes.

  • Will

    “Test HTML mockup in as many browsers and versions as possible. (You might need to employ a few friends if you only have one computer.)”

    Or, you could make use of browsershots.org. :)

  • http://www.mabucplus.com Mark Abucayon

    wow I love this one…very interesting article love reading this one. thanks guys for this article great job..

  • http://www.simonjs.co.uk simonjs

    I came across the a fluid version of the 960 grid system whilst looking into it a while ago. Although I haven’t used it yet, it looks quite promising from the demo:

    http://www.designinfluences.com/fluid960gs/

  • http://reiem.blogspot.com ilovecolors

    I’ve found quite useful the 960 base psd and the sketch sheets although I won’t be using any framework, simply because of 1) the time involved in learning all the stuff, 2) it could have bugs and 3) the code size, which I don’t want my users to download over and over. However, for starters, it’s a great start, just make sure you don’t stay too much there without watching the backstage. I do use a reset.css from Yahoo! UI library, and it’s cool. Great site btw, keep it up!

  • http://www.colinmiller.co.uk Colin Miller – Freelance web designer

    Very useful article. Coming from a trained graphic design background, the use of grids is standard practice (print). Designing grid systems for web sites can be painful, so this article was very informative. Thanks

  • http://www.dakeat.com dakeat

    Solid introduction and basic comparison. While I am still a fan of creating my own “frameworks”, there is no denying the time that could potentially be saved with one of these prefabs. I have yet to try one on a project since I am a fan of using classes and id’s that have a bit more relative meaning. I’ll have to give one a test drive one of these days.

  • http://www.gimpstraw.com/ Nathan

    I’ve only used Blueprint, I liked it but I didn’t like the fact you had to add extra tags for IE or the margin it leaves on the right. So, I just wrote my own based off of it. My framework is based off of a 10px wide system, which I feel gives you more control over the widths over Blueprint.

  • Frederico

    I guess there is no way to avoid making myself look stupid here, but where would I learn how to design with grid framework?

  • http://www.rajdash.com/ Raj Dash

    A few clarifications/ notes/ arguments are in order…

    Blueprint IS NOT fixed to 950 pixels wide, nor to a 24-column grid. This seems to be a common misunderstanding, so I probably didn’t explain it well. That is merely the default (30 pixel wide columns, 10 pixel wide gutters). You have a lot of control over this. Use Kematzy.com/blueprint-generator to design your own custom Blueprint grids, but save time by not having to devise new CSS classes. So if you prefer a 960 px wide grid, you can rebuild the framework. Fast.

    Stylesheets are only loaded once into a visitor’s web browser. They won’t be loaded over and over. But yes, the HTML page COULD be reloaded. Still, unless you overdo the custom classes, the comments that you’re getting bloat from the extra HTML div tags and classes seem a little overly concerned. You’re really not adding that much more in total bytes. What’s more, if you wanted to achieve the exact same grid layout (effectively) using your own CSS classes instead of Blueprint (or whatever), you would have to add your own bloat”. So unless I’m missing something, I can’t see how this argument is valid. Read Philm’s comment, which more eloquently says what I’ve tried to say in the article.

    Dirk/ djesse: I don’t think I described the quality of YAML based on tha lack of use. But I guess I did miss the CC license. Thanks for pointing that out.

    General comment: I did say that grids are a framework. You can pull them out. They’re not all bloated, despite comments saying otherwise. But if you dont’ want to use them, you not have to replace a CSS framework with your own CSS + div “bloat”, to achieve the same effects? From scratch. I don’t know about you, but as a former active programmer, I like to find short cuts that don’t “cost” a lot. Why would I create a whole new set of CSS classes when it’s ready and waiting in a CSS grid framework?

    I’m not a web designer, but I’ve done a lot of print layout. I used grids a lot. To me, it seems illogical not to use grids in web design, whether custom or with a framework.

    Frederico: There is a tutorial coming that shows how to design with Blueprint. After that, I’ll be doing futher tutorials that use Blueprint, but do not focus on that aspect.

  • http://www.mindplay.dk mindplay.dk

    Comparing my Grid Designer to Blueprint is probably a bit irrelevant – it was not designed as a framework, merely as a utility to help you design your horizontal and vertical grid specifications.

    Whether you choose to apply what you designed in a handcoded CSS environment, or one based on Blueprint or another framework, is up to you.

    If you use Blueprint, one of the things you might find my Grid Designer incredibly useful for, is the vertical grid design – the typography. Something that a lot of people seem to forget, is that grids have two dimensions…

  • Thiago Menezes

    Ahhh!! Sometimes I feel there’s too much to read! Look at that amount of links!

  • http://www.pairacy.com Pai

    i used to use blueprint.. until recently i switched to 960.gs..

    both does the job pretty well anyway.. :)

  • http://notaniche.com Not A Niche

    Hey Raj,

    you might be surprised, but there is a theme which is using YAML, and not only that. With some clicks in your admin it’s possible to change the layout to a sidebar on the right or on the left or having two sidebars. And many more changes are possible just with some clicks in your admin. Check out the video on this page

    http://dynamicinternet.eu/wordpress/wordpress-themes/yaml-green-theme/

    Unfortunately the page is only in German but check out the video and you will understand. Very cool. A new way of adjusting your WordPress template

  • Pingback: socialcmsbuzz.com

  • http://foohack.com Isaac Z. Schlueter

    Hey, just thought you should know, it looks like someone is ripping off your content:
    http://cssdevkit.com/?p=55

    –i

  • http://www.benoitdeziel.com Benoit Deziel

    First of all, those CSS frameworks aren’t totally templates, because the grid system isn’t one. If so, many designers in the print industry would have used templates for decades. I’ve done print design and I think those CSS frameworks give a solid foundation to start a great design. As a web designer, I use 960.gs or Blueprint on every projects since 6 months or so, depending on my design choices. Those frameworks don’t limit your creativity, they help you design a more robust, flexible, consistent web site.

    My point is, no matter if you use one of those frameworks or create your own, design on a grid system and you’ll be happy with the result.

    If you fill that there is to much code in these frameworks, just delete the code your not using. Better yet, modify the code and keep it as your own framework. For Blueprint, the source code is release under a MIT License, so you can do whatever you want with it. Also, there is some generator for Blueprint to fit your needs.

    And for those who are concerns about divitus, if you know how to use those frameworks right, you can still make your code semantic by using multiple class names.

    So my choice is to stick with CSS Frameworks and modify them to my needs to keep the code unbloated and the lightest as possible.

  • http://www.rajdash.com/ Raj Dash

    mindplay.dk: Thanks for clarifying that. I should have put Grid Designer under the “tools” category.

    Thiago: Well, no need to read them all right away :)

    Pai: Not surprising since one of the 960 developers also had a hand in Blueprint.

    Not a Niche: Thanks for the heads up. As thorough as I tried to be, I never came across any. Thanks for the link.

    Isaac: Thanks for letting us know. It appears that the page is gone, so Collis might have dealth with it.

    Benoit: Exactly. Good argument. As for print design templates, are you sure? I worked in Pagemaker a great deal and I had a couple of layout templates – basically blank Pagemaker files with a grid set down from the first time I created the “layout”. It saved me so much time when putting together an issue of my print magazine.

  • Pingback: links for 2008-06-21 « Mandarine

  • Pingback: Grids « Website redesign

  • http://www.expoweb.cl Paula Sáez

    Muchas gracias por los tips, desafortunadamente no entiendo muchas veces el idioma. Asi estudiare Inglés tambien. Un saludo cordial a los sres de Nettuts

  • travist

    Great article, interesting design approach.

    I tend to agree with a lot of the comments here, in that CSS grids are really not necessary. I’ve spent a lot of time trying to really be effective with using all of blueprint for a recent design. And while I feel like there are some interesting concepts I’ve learned (and even has included them in my own custom css), the concept of a framework is too limiting. If you can put your design in the box, it will work fine. But, I don’t want to be beholden to artificial constraints created by a framework, i’d rather let technology and client requirements be my constraint.

    The other really, really annoying thing about blueprint is the 960px factor. I ended up using the blue print grid generator to generate a 900px model, but even then there’s lots of pain… so I’ve decided to not use it for my current design. Who knows, maybe I’ll give it a go again, but the for time being, I’m going to have to give this the thumbs down.

  • http://www.medications-store.com Dirk

    Yea !! Sometimes I feel there’s too much to read! Look at that amount of links! Thanks for all.

  • Pingback: 50+ Articles to Make You a Better Web Designer | DesignM.ag

  • http://www.targetict.com neil

    detailed article thanks! the Blueprint framework looks good

  • Chad

    Gotta say that I’m not a fan of the Frameworks. It just seems a bit “bloated”. But I have to admit, I do use the 960 grid for a Photoshop layout occasionally. But all of my HTML and CSS (outside of Meyer’s reset.css) is all by hand. I just find it more managable.

  • http://www.windows7themes.com Windows Themes

    That is fantastic Raj. Thank you for this well written tutorial !

  • http://www.londonrecowery.co.uk sklepy internetowe

    very interesting article thx is very helpful

  • Pingback: Creative glo - website design, HTML and CSS coding » CSS frameworks part 1

  • http://URL(Optional) Gerald

    The web is not a grid, OK, lets get this strait. For years accessibility and SEO experts have been telling us to stop using grid based layouts and start using semantic source ordered markup.

    Grids is a step back in time, a degeneration of the web, not an improvement. Its little more than the dam designers running amok, again. Think tables but this time with divs, not quite the same same, but very nearly.

    Stop using grids NOW. They are bad for the web and bad for your health, nothing more than a flash in the pan fashion that god help us all passes by quickly so we can get back to building a web that actually works.

    I’ve been a web designer for over 10 years, apart from that horrible period of font tags and tables, this is the worst thing to come along in years.

    • factotum218

      Sorry, I know this is 3 years old but I can’t help it. Accessibility and SEO experts that you speak of don’t understand that the semantic order of the markup and the CSS positioning of divs and/or semantic block elements are two completely different things. You can take a prim and proper order of an (X)HTML document and turn it completely inside out with CSS without optimization coming up short. Therefore the Grid system you use has nothing to do with impairing the SEO of any block element order you choose in the (X)HTML document.

      You also seem to think that a grid system is rigid and cannot be slimmed down or altered. This is also not true. Many people use grid systems to further understand layout principles by stripping down what isn’t being used after their layout is complete. It’s extra work, but that’s part of the learning process to become an efficient and knowledgeable developer. Soon after they aren’t using grids, their creating on their own.

  • Pingback: Websites you shouldn’t have missed in May 2008 | Noupe

  • Pingback: Two big Time-savers for Web Designers | Conceived

  • http://defineyourcolors.com/ Vincent Murphy

    Grids are only bad when used badly. Like any framework, the benefit is in having a documented solution that a whole team can use. When trying to manage multiple people and content, having a standard that’s documented is a godsend.

    They lose their usefulness for single-person set ups or for small sites.

  • Pingback: Upmedia.dk | weblog for Uffe Petersen » 50+ Articles to Make You a Better Web Designer

  • http://www.WebDevelopment2.com/ Baz L

    It seems I’m a bit late to the party here. I’ve heard the arguments against CSS frameworks, but they all seem to be very localized.

    Designers in general like to feel good about “their design”. It makes them feel all warm and fuzzy that they did it all on their own.

    Me on the other hand; I don’t have that kinda need or time. I just want it to work, that’s it. Now seeing the number of very large/popular sites out there that just have some nasty code behind them, the whole idea of CSS Frameworks breaking semantics is lost on me. Again, I just want it to work.

    Now for simple layouts: few columns, etc. they are overkill. However, if you want to get something like a magazine-type layout up and running with a minimum of muss and fuss, they’re a godsend.

  • anzaan

    @Gerald
    Its sad that even with 10 years of web designing, u don’t seem to understand designs.
    My brother is an artist, his speciality is water color. Mostly he designs by just sketching out coarse outline in pencil and applying color to the canvas.

    But when he need precision in his art for say a potrait, he draws out grids in canvas with pencil and starts sketching and then fills up the sketches with paint, and the paintings come alive.
    He is a self taught artist and though he never took art classes in his school or anywhere for that matter , yet intuitively he uses grids to get a better layout and precision of his paintings when situation demands

    What does that tell you??

    Maybe nothing , maybe something…..

    As for me. it tells me that grids help us organise/arrange content in a layout in an intutive way, be it an artist’s canvas or a web developer’s HTML markups.

    But, on the other hand, using CSS for layout is a fundamentally flawed concept. The concept of emulating table layout with a ton of CSS hack has a serious flaws. BOX-Model is conceptually flawed model for designing layouts.
    Common sense tells me that if something has a borders and paddings, those structures should be contained within that element that gets decorated. It shouldn’t affect its surrounding environment.

    Think of it this way. If you want to create fences around your house compound, do you force your neighbour to restructure his house and his compound so u can add a fence (border?? ) or do u just build a fence within your compound??
    What if you want to build a really thick wall? Does that mean your neighbour had to make a bigger adjustment? IF your neighbour’s house is very close to the border of your compound, does that mean that your neighbour has to demolish part of his house to accommodate your really thick walls??
    Think about the chaos it ensues were things like that in reality.
    The side-effect of any structural changes or decoration should only effect only that element and the rest of the elements in your layout shouldn’t have to suffer as a consequence.
    Makes sense?

    Pragmatism tells me that tables make more sense for layout, but of course all CSS purist will gasp in horror when they hear it.
    Everytime someone says they prefer Table based layout or hybrid layout, the purists seem to think that those people are against CSS.
    Well, that’s not the case, my friend. I use a lot of CSS, for presentation, and I use tables for layout where it makes sense while all the semantic purist bleed to death trying to fix content that bleeds out of thier semantic site.
    But on the subject of using frameworks, it makes a whole lot of sense to use a framework if you do want to retain your purist status because think about it, how often do you get access to all browser derivatives for testing purpose?? FF 3.0 and IE7 are the only readily available unless u work for a huge company that has a mature test environment.
    As for me, I’m looking into using YUI CSS Framework for a project.
    Why YUI ? because I haven’t seen a screwed up YAHOO site and that tell me that if its good for them, its good enough for me. At least I won’t have to test it on browsers I don’t have access to as they do all the regorous testing.
    And, YUI has lot more to offer than just CSS Framework, they have excellent Javascript library that I use in pretty much all projects these days. I use their library because they practice what they preach. All of their sites use YUI javascript library and CSS Framework. And they are cross-browser complaint too.

    Before complicating things too much with purist headset, one should ask themselves a very important quesiton. Is CSS/DIV layout answer to all question?
    IF not are there other alternatives to your problems?
    IF so and if the alternatives work for you what will stop you from using it??

    Oh, I know the answer to the last question for most purists and CSS-P fanboys. ” But, its semantically incorect…. and it has previeced drawbacks and blah ri blah”.
    One thing to keep in mind is all these damn tools available to us has only one purpose, to aid us in our development. So they are supposed to serve us.
    So the question is, what are semantics for? I don’t serve CSS or W3C, I make css serve me the way I see fit for a given situation.
    IF CSS doesn’t work for me I don’t cry myself to death or spend days trying to solve something that can be done in an hour using something else.

    Amen