Among environmental designers, the word “css framework” is becoming more and more popular. But what is it? What are the benefits and drawbacks are we facing here. Below you will find the first part of the article on css framework.Certainly, very often you have been assigned the task of creating pages from scratch. You usually follow a standard route. You look for inspiration, make a few mokup, then you develop Disign, and here the real challenge begins.
Again, you are confronted with the task of implementing your vision into life. And here difficulties come up, once again the need to write the same rules for different layouts and copy what has been done dozens or even hundreds of times.
Luckily, we get the predefined rules at our disposal more often now. Imagine that the entire work on which involves creating the appropriate layout suddenly disappears and you are provided with well described, and properly working rules. You stop worrying about compatibility in seven browsers (especially IE6). What you need here would be just well-defined blocks and their nesting, adding the appropriate class and … Voila!!
Using frameworks has its advantages which I’m presenting below:
1. Compatibility with most browsers.
2. Preservation of purity and consistency of code.
3. Increases work efficiency.
4. Unification of the rules used.
Everything sounds perfects but is it really the case? Indeed, all the above mentioned arguments are very compelling, but don’t you have the impression that this is simply a set of common-sense rules that should be followed by any “good” webmaster / web designer? But try to think what would happen if the client expected from us a custom solution for something unique, and then what the response would be … “Unfortunately we are not able to do it as this framework doesn’t allow it… sorry … but you can choose something from thousands of layouts available ….” What if his vision is the thousand and first and our framework does not handle it.
Using this type of solutions we are also “forced” to apply rules which are not always clear and understandable, by simply trying to imitate what was made available without demanding any particular interest and studying from the developer.
Like with every framework there are disadvantages:
1. It doesn’t allow allow non-standard behavior.
2. It involves copying previously collected rules and thus copying mistakes.
3. Wasting time on becoming familiar with the solution.
4. Problems with the semantics of code.
I cannot unanimously determine whether the technology I am discussing here is good or bad. I think the truth lies somewhere in the middle. In my opinion (and not only mine) using this type of solutions is suitable for small websites and the standard ones that are “mass produced”.
It may prove really useful when you have to do something urgent and quite standard, without involving large financial or human resources. Personally, I prefer to do everything myself, master my skills and know the website I’m building inside out.
Share your experiences with CSS framework below by leaving a comment. Follow us on Twitter at @GOYELLO.
We process cookies and make them available to Google Analytics (a service provided by Google, Inc.) to improve the performance of the website, to learn your preferences about using it and to tailor it to your needs. The data will be anonymised before being transmitted. If you do not agree to this, you may disable cookies in your browser. If you do not change your browser settings, you accept the fact that it saves cookies.