Despite the high levels of creativity and diversity amongst WordPress themes there are always going to be parts of the theme that are similar. WordPress provides the template tags to get this information out, but it should it also provide a framework for presenting this information?
I’m not suggesting that WordPress should come bundled with blueprint, perish the thought, or that themeing should become a sandbox excercise; however, I do wonder if there are some tasks that can be accomplished centrally to make it easier for anyone producing a theme.
It would be a simple matter to develop a base library that can be included using a theme tag or, even better, to have some background processing that would output a stylesheet to your basic specifications.
Imagine:
[php]
Obviously something like the example would make a lot of assumptions and you may need to override them in the theme stylesheet proper, but to have that option might help to set new standards for theme production, as well as making it quicker and easier to do.
So what do you think? Should WordPress have its own CSS theme framework?
(__)
`
[...] 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? [...]