Markup and Cascading Style Sheets

The World Wide Web Consortium originally created Cascading Style Sheets so that it would be possible to write web pages without weighing down the html with a lot of extra code creating with styling commands. Because Cascading Style Sheets allow designers to make generalized changes through the use of commands specific to them as well as classes, and they do not impose storage constraints, they allow webpage designers a lot more freedom in their work.

Some of the problems with Cascading Style Sheets to do with the fact that they are written in ASCII are that a) the writer must know English in order to utilize them, and b) the writer must be very exact, and cannot make any mistakes in the code, or else it will not turn out the way s/he intends it to look. Therefore, Cascading Style Sheets require a certain amount of prior knowledge to create. They are not accessible to the wider public. Fortunately, this problem has been realized by software developers, and templates, like the one I have used for this blog, have been created for those who are not as familiar with HTML, resulting in the surge of internet usage around the world.

I created a few of my own cascading style sheets that I have applied to my webpages by creating an internal style sheet, which I linked to the html documents that I had already written. I chose an internal style sheet over external and inline style sheets because I wanted to create a unique style sheet for each page, and I wanted to separate the style of the words from the content of my html.