[...] Should WordPress have its own CSS framework? [...]

[...] Read full article (via wp-fun.co.uk) Tags: css, development [...]

[...] Should WordPress have its own CSS framework? [...]

[...] Should WordPress have its own CSS framework? [...]

Di, in general I don’t like frameworks for those reasons. But I generally feel that there is scope for using them as defaults or helpers, but I wouldn’t want anything like blueprint.

Whenever I’ve looked into frameworks they’ve always seemed either too restrictive, meaning I’d spend more time undoing stuff the developer put in, or they are bloated with loads of unnecessary code for my design. I don’t think WP theme designers would benefit from a framework and hobbyists would probably end up ignoring what they don’t understand and build the CSS in Word anyway :P

Curtis, a plugin would certainly do the job; however, that would mean theme authors couldn’t rely on it being there. They would probably then need to either reinvent the wheel or include their own version.

Ryan, do you not think there is an attraction for theme authors in being able to use one line to get their typography set up to an acceptable standard or to the community as a whole from knowing that themes all meet that standard? Is there no benefit to be had by highlighting the existence of the methods they include, or of raising the baseline for theme authors?

No.

I can’t understand why anyone would want this.

Interesting idea, I love CSS frameworks but I don’t know if one needs to be built into WordPress. I think a plugin would be a better choice, so you could pick which framework you wanted.

I personally probably wouldn’t use it but I’m sure some people would like it.

[...] Should WordPress Have Its Own CSS Framework? [...]