Thursday 19th of April 2018 05:19:46 PM

CSS Style Guide


This Style Guide explains the markup and design requirements for web projects, along with various standards and best practices.

projects authored in valid XHTML 1.0 Transitional and styled with valid Cascading Style Sheets will be described here. See the XHTML and CSS sections below for details. Additional sections of this Style Guide, coming soon, will provide information on writing for the web, naming and filing your documents, and other useful topics and guidelines.

XHTML: Guidelines & Benefits

Library projects must be authored in structural XHTML 1.0 Transitional. Page authors should follow accessibility guidelines in compliance with U.S. Law, and so that our site’s content will be made available to the widest possible number of people, browsers, and Internet devices. In addition, all XHTML must validate.

XHTML Guidelines
The rules of XHTML as compared to HTML—an easy transition
What is XML?
A brief introduction to the foundation of XHTML
XHTML Benefits
Four key benefits of converting from HTML to XHTML
XHTML Authoring Tips & Tools
Simplifying the work process—includes tips on thinking structurally, and tools for hand-coders and Dreamweaver users
XHTML Accessibility Tips
Making sure your pages can be read by all visitors, browsers, and devices
XHTML Validation
Ensuring interoperability by avoiding errors and sticking to standards

CSS: Style Sheets & Tips

Library projects must use valid Cascading Style Sheets (CSS) to control typography, color, and other layout elements. Style Sheets must be linked in a way that accommodates the capabilities of new and old browsers.

CSS Guidelines
Tips on authoring and linking to Style Sheets
Steal These Style Sheets!
Style Sheets for your use in Library projects
CSS Validation
Ensuring that your Style Sheets are error-free (same as XHTML validation)

A number of valid Style Sheets have been provided for your use. If you wish to create your own Style Sheets, please discuss your requirements with the Branch Library’s Web Coordinator.

might decide later to make all subsection titles dark red instead ofdark blue, and the statement H2.dkblue {color:maroon;} is a little silly.

From this simple example, we draw the general lesson that whenyou're planning to use styles, it's generally to youradvantage to plan ahead and use all of the tools you can. To take thepreceding example a little further, suppose that a navigational baris added to the page. Within this bar, hyperlinks should be yellow,

link popularity
that is heavier than is normal for the document, as shown in Figure 5-8. This is what we're used to, of course,since B does cause text to be boldfaced.

Figure 5-8

Figure 5-8. Making the B tag bold

However, what's really happening is that a heavier variant ofthe font is used for displaying a B element. Thus,if you have a paragraph displayed using Times, and part of it isboldfaced, then there are really two variants of the same font inuse: Times and TimesBold. The regular text is displayed using Times,and the boldfaced text uses TimesBold.can handle all three.Here's a link to my e-mail: so you can complain about this page.  The link encloses both the image(with default border) and the blue underlined text.  Note that I specifiedthe text for the subject line (the sender can change this). I could alsospecify ?cc= or ?bcc= and list e-mails to receive copies or blind copies.Navigator handles any one of these options; Explorer can handleall three.and Kursiv are usually mapped to the italic keyword, while oblique can be assigned faces with labels such as Oblique, Slanted, and Incline.

If you wanted to make sure that a document uses italic text in is not listed in the browser's history).


This pseudo-class applies to hyperlinks, but not named anchors. It sets the styles to be used for a hyperlink that points to a URI that has already been visited (i.e., is listed in the browser's history).

anchor elements with an HREF attribute

A shorthand way of expressing the various background properties using a single rule. Use of this property is encouraged over the other

Even though the LINE tags don't exist, thesituation is the same as if they did. Each line of text inheritsstyles from the paragraph, so they may as well be contained withintags such as these. Therefore, the only reason we createline-height rules for block-level elements is sothat we don't have to explicitly declare aline-height for all its inline elements, fictionalor otherwise.