Contents
In this tutorial, we show how easy it can be to design simple style sheets. For this tutorial, you will need to know a little [HTML40] and some basic desktop publishing terminology.
We begin with a small HTML document:
<HTML> <TITLE>Bach's home page</TITLE> <BODY> <H1>Bach's home page</H1> <P>Johann Sebastian Bach was a prolific composer. </BODY> </HTML>
To set the text color of the H1 elements to blue, you can write the following CSS rule:
H1 { color: blue }
A CSS rule consists of two main parts: selector ('H1') and declaration ('color: blue'). The declaration has two parts: property ('color') and value ('blue'). While the example above tries to influence only one of the properties needed for rendering an HTML document, it qualifies as a style sheet on its own. Combined with other style sheets (one fundamental feature of CSS is that style sheets are combined) it will determine the final presentation of the document.
The [HTML40] specification defines how style sheet rules may be specified for HTML documents: either within the HTML document, or via an external style sheet. To put the style sheet into the document, use the STYLE element:
<HTML> <TITLE>Bach's home page</TITLE> <STYLE type="text/css"> H1 { color: blue } </STYLE> <BODY> <H1>Bach's home page</H1> <P>Johann Sebastian Bach was a prolific composer. </BODY> </HTML>
For maximum flexibility, we recommend that authors specify external style sheets; they may be changed without modifying the source HTML document, and they may be shared among several documents. To link to an external style sheet, you can use the LINK element:
<HTML> <TITLE>Bach's home page</TITLE> <LINK rel="stylesheet" href="bach.css" type="text/css"> <BODY> <H1>Bach's home page</H1> <P>Johann Sebastian Bach was a prolific composer. </BODY> </HTML>
The LINK element specifies:
CSS can be used with any structured document format, for example [XML]. In fact, XML depends more on style sheets than HTML since authors can make up their own elements which user agents don't know how to display.
Here is a simple XML fragment:
<ARTICLE> <HEADLINE>Fredrick the Great meets Bach</HEADLINE> <AUTHOR>Johann Nikolaus Forkel</AUTHOR> <LOCATION>Potsdam</LOCATION> <PARA> One evening, just as he was getting his <INSTRUMENT>flute</INSTRUMENT> ready and his musicians were assembled, an officer brought him a list of the strangers who had arrived. </PARA> </ARTICLE>
To display this fragment in a document-like fashion, we must first declare which elements are inline (i.e., do not cause line breaks) and which are block-level (i.e., cause line breaks).
INSTRUMENT { display: inline } ARTICLE, HEADLINE, AUTHOR, LOCATION, PARA { display: block }
The first rule declares INSTRUMENT to be inline, and the second rule, with its comma-separated list of selectors, declares all the other elements to be block-level.
It's not yet clear how style sheets will be linked to XML documents, but assuming the above CSS fragment is combined with the XML fragment, a visual user agent could format the result as:
Fredrick the Great meets Bach Johann Nikolaus Forkel Potsdam One evening, just as he was getting his flute ready and his musicians were assembled, an officer brought him a list of the strangers who had arrived.
Notice that the word "flute" remains within the paragraph since it is the content of the inline element INSTRUMENT.
Still, the text isn't formatted the way you would expect. For example, the headline font size should be larger than then rest of the text, and you may want to display the author's name in italic:
INSTRUMENT { display: inline } ARTICLE, HEADLINE, AUTHOR, LOCATION, PARA { display: block } HEADLINE { font-size: 1.5em } AUTHOR { font-style: italic }
[add image, description]
Adding more rules to the style sheet will allow you to further improve the presentation of the document.
This section presents one possible model of how user agents that support CSS work. This is only a conceptual model; real implementations may vary.
In this model, a user agent processes a source by going through the following steps:
Part of the calculation of values depends on the formatting algorithm appropriate for the target media type. For example, if the target medium is the screen, user agents apply the visual rendering model. If the destination medium is the printed page, user agents apply the page model. If the destination medium is an aural rendering device (e.g., speech synthesizer), user agents apply the aural rendering model.
Step 1 lies outside the scope of this specification (see, for example, [DOM]).
Steps 2-5 are addressed by the bulk of this specification.
Step 6 lies outside the scope of this specification.
For all media, the term canvas describes "the space where the rendering structure is rendered." The canvas is infinite for each dimension of the space, but rendering generally occurs within a finite region of the canvas, established by the user agent according to the target medium. For instance, user agents rendering to a screen generally impose a minimum width and choose an initial width based on the dimensions of the viewport. User agents rendering to a page generally impose width and height constraints. Aural user agents may impose limits in audio space, but not in time.
CSS2 selectors and properties allow authors to refer to the following "entities" from within a style sheet:
CSS2, as CSS1 before it, is based on set of design principles:
Backward compatibility. User agents supporting CSS2 will be able to understand CSS1 style sheets, while CSS1 user agents are able to read CSS2 style sheets and discarding parts they don't understand. Also, user agents with no CSS support will be able to view style-enhances documents. Of course, the stylistic enhancements made possible by CSS will not be rendered, but all content will be presented.
Complementary to structured documents. Style sheets complement structured documents (e.g. HTML and XML), providing stylistic information for the marked-up text. It should be easy to change the style sheet with little or no impact on the markup.
Vendor, platform and device independence. Style sheets enable documents to be remain vendor, platform and device independent. Style sheets themselves are also vendor and platform independent, but CSS2 allows you to target a style sheet for a group of devices (e.g. printers).
Maintainability. By pointing to style sheets from documents, Webmasters can simplify site maintenance and retain consistent look and feel throughout the site. For example, if organization's background color changes, only one file needs to be changed.
Simplicity. CSS2 is more complex than CSS1, but it remains a simple style language which is human read- and writable. The CSS properties are kept independent of each other to the largest extent possible and there generally only one way to achieve a certain effect.
Network performance. CSS provides for compact encodings of how to present content. Compared to images or audio files, which are often used by authors to achieve certain rendering effects, using style sheets will decrease the size of the content. Also, fewer network connections have to be opened which further increases network performance.
Flexibility. CSS can be applied to content in several ways. The key feature is the ability to cascade style information specified in: the default UA style sheet, user style sheets, linked style sheets, the document head, and in attributes for the elements forming the document body.
Richness. Providing authors with a rich set of rendering effects increases the richness of the Web as a medium of expression. Designers have been longing for functionality commonly found e.g. in desktop publishing and slide-show applications. Some of the requested rendering effects conflict with device independence, but CSS2 goes a long way of granting designers their requests.
Alternate language bindings. The set of CSS properties described in this specification form a consistent formatting model for visual and aural presentations. This formatting model can be accessed through the CSS language, but bindings to other languages are also possible. For example, a JavaScript program may dynamically change the value a certain element's 'color''color' property.
Accessibility. Last, but not least, using CSS will increase accessibility to Web documents. By retaining textual information in text form, both robots indexing Web pages and human users will have more options for digesting the content. Users can provide their personal style sheets if author-suggested style sheets hinders accessibility. The cascading mechanism negotiates between, and combines, different style sheets.