I have been reading up on CSS frameworks, to see if it could be useful for an intranet that I am helping to build, but the true purpose does not become clear to me. What circumstances would the deployment of a CSS framework be useful in? What does a CSS framework do that a CMS template cannot do?
I personally feel that CSS frameworks are a bad idea.
If you stick with regular CSS, you are using the lowest common denominator and will be 100% compatible with anyone, can go anywhere. With the framework, you are stuck in that system, have backed yourself into a corner.
With regular CSS, you can validate the code to the point where there are zero errors. With the framework, that may not be possible. There might typically be errors in the framework code itself. You can't change that code, you're stuck with it.
With regular CSS, anybody can look at your files and understand them. With the framework, only the limited group who understands that special framework can make sense of your files.
With regular CSS, you will become expert at CSS, and can apply that knowledge anywhere. With the framework as a crutch, you may never really learn CSS.
I'm sure there are advantages to using a framework. Maybe if you are doing something quick and dirty, it's a good idea. But for the long run I think you are better off with CSS, either as part of a web site template or something you write from scratch.
1 Like