I've been reading up on building websites on CSS Blueprint. I think I get the drift to make websites more standard, but it seems like I'm doing stuff I used to do when I didn't really know what I was doing: using a template and rip out what I don't need.

Now, the advice is to start planning the css before you start designing in Photoshop, which is awkward for me, but ok, I think I can adjust to that.

Who's using it, who's liking it?

I'm not using it. I think the principle is cool. It allows you - once you have had some practice - to quickly create mock ups to show a client. I wouldn't recommend it being used in a real world environment. However to get something on the page quickly I think its excellent.

The problem I have with it is that it will always contain code which I will not require. This will be loaded with a webpage. On the plus side if it is used on real world websites it will create uniformity across your websites making it easier to style new pages. Furthermore it reduces the likelyhood of styling errors.

I've used YAML before... quite similar.

As I am new to CSS and am learning, are these programs good to download to play around with to see how to structure correctly. Or do they make people lazy.

That's a very good question. I'm not sure what the answer is.

I've never used a CSS framework. Since I am now expert in CSS, I think I would find frameworks annoying and perhaps limiting. For me, a CSS framework would only be useful if it saved me time; and I suspect that it wouldn't. At least when I write my own CSS, I know exactly what's going on.

Nevertheless, I can see how a framework could be a good choice. In particular, a good framework will protect you from some of the nasty IE bugs.

A possible downside is that, given the investment of time required to learn the framework, you might as well just learn CSS. But it's hard to judge this trade-off.

If you do choose to use a CSS framework, bear in mind that they split CSS into modules -- core.css, layout.css, typography.css, and so on -- which increases the number of HTTP requests for your page. This can dramatically increase response time, because all these CSS files need to be fetched before the page can be displayed. In my experience, consolidating all your CSS files (per media type) greatly increases the apparent speed of your website.

You could of course consolidate the framework into a single CSS file.

But I think the .PSD for the framework is useful for designing a website. Because you use the grid it's easier to align and create designs that are easier on the eyes (dunno how to explain, but I think you catch my drift)

Just looked at the Blueprint web page, and saw Eric Meyer's name associated with it. Is he not meant to be one of the top notch guru's of css?? What I mean is if he is involved, then it can't be all that bad

Sorry I read that wrong. It is based on his work, which is different

This post has been edited by thewal: Jul 4 2008, 05:30 PM

Oh, no, no.. The Blueprint is a great idea, and it can have some great advantages, but Adobe is a big guy in web design as well, but their Photoshop still works with slices, tables or absolute div's. What I'm trying to say is: you don't always have to follow what the big boys do..