| p>Introduction | | | | response of a site, I am sure. Shorter code pieces |
| When the Internet web sites started delivering | | | | are easier to develop and easier to maintain too. |
| content it was always to the computer screen. One | | | | Being less complicate, kind of higher level structure |
| could then create the HTML code that structures | | | | oriented, the code will be less error prone too. On |
| content to include code that takes care of the | | | | large projects the cost savings could really be very |
| display peculiarities. So you had to specify the fonts, | | | | significant. When this higher level formatting data |
| its size, color and so on. Very soon it was the printer | | | | such as headers etc are used, it is easier for the |
| at the user site that needed to be addressed. Only | | | | search engines to identify then compared to if the |
| way to do this was to create another page that is | | | | header information is combined with font attributes |
| suited to the printer issues. | | | | too. Overall there is another saving on a recurring |
| Very soon there was a proliferation of display | | | | basis. When you have visitors and many of will be |
| devices-the presentation devices that interpret the | | | | using quite a bit of download bandwidth. When you |
| HTML code downloaded into a presentation suitable | | | | use a web hosting service they typically charge you |
| for the specific device. The device, today can as well | | | | on the bandwidth usage. Larger pages obviously are |
| be a smart phone! In fact, even for mobile devices | | | | less efficient besides the other issues. |
| there was an attempt to create special pages that | | | | Downsides Of CSS Use! |
| had embedded code that addresses the needs of | | | | Is everything great then when you use CSS based |
| these devices. Now imagine the hassle of creating | | | | development of web sites? Unfortunately there are |
| content for many of these device types, each a | | | | some practical problems associated. Like most other |
| specialized page tweaked for the specific device. Let | | | | standards, if everybody followed and implemented |
| us not worry about older and newer versions of the | | | | standards the same way, things would be fine. Many |
| devices etc for now. Imagine doing this for hundreds | | | | feel getting rid of the CSS approach may be a better |
| of pages of your website for may be ten of the | | | | option because of these hassles. Because of the |
| device types. The combinations can blow up very | | | | various glitches, best possible fit to a presentation |
| quickly! | | | | device is handmade HTML pages that include all the |
| How Does CSS Help! | | | | font information, placement and spacing information |
| Once a separation is made like that the development | | | | etc. You are able to tweak things down to a pixel on |
| becomes much simpler. Develop just the HTML code | | | | the display face. |
| for the simple structure of the content. If style | | | | While CSS specifications have progressed from CSS 1 |
| information is taken out the basic code for the | | | | to 2 and then 2.1, browsers have been slow in |
| content is really small. One CSS is developed per type | | | | implementing them. Quite often wrong assumptions |
| of presentation device. Say you have 100 web pages | | | | were made and features did not work the way it |
| and are addressing then the development effort is | | | | should. As of July 2008 none of the production |
| only 100 HTML page code development time+ N* | | | | version browsers had the CSS 2.0 features |
| CSS development time instead of 100*N content | | | | completely and correctly implemented. Situation with |
| development time(that includes HTML+ style code). | | | | CSS 2.1 is obviously worse. Biggest problem with |
| If these style sheets are done centrally by one | | | | these issues is that developers have to do work |
| group and the focus is on a standard style much as a | | | | arounds that are specific to browsers. One the one |
| branding strategy, there is a uniformity of style on all | | | | hand then you need to do extensive testing across |
| web pages. | | | | browsers for the effects of both these phenomenon. |
| Now your web pages are much smaller as they | | | | Maintenance also becomes very time consuming as |
| contain smaller amount of HTML code in them. Do | | | | the code tricks and wok arounds used could be |
| they have an impact on the load time? There is no | | | | difficult to understand. Both these effects lead to |
| prize in guessing that it the load time of a page | | | | higher costs obviously. |
| improves. But, one can argue if 10 ms vs. 3 ms in | | | | Conclusion |
| page load times make a difference! For an | | | | As devices that can access the Internet proliferate, |
| e-commerce site that may mean the difference of | | | | mobiles, netbooks, mobile internet devices, the case |
| ability of holding attention of those choosy visitors | | | | for keeping content structure and presentation |
| and that could be a crucial difference. The time | | | | gathers strength. There is no other way to go. The |
| improvement is of several orders as the code | | | | problems with CSS are similar to problems that has |
| reduction is very significant when you take out all the | | | | happened with implementation of other standards. |
| font, color attributes and the content positioning | | | | Until all the pieces fall into place problems would |
| commands in the HTML code necessary to take care | | | | remain. One just has to wait and watch! |
| of presentation. That is bound to show up in overall | | | | |