Saturday 26th of July 2014 07:12:44 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.

link popularity
the left-floated image, as depicted in Figure 8-32.

Figure 8-32

Figure 8-32. More overlap prevention

4. A floating element's top may not be higher than the inner top of its parent.

Another simple rule. This one keeps floating elements from floating all the way to the top of the document. The correct behavior is illustrated in Figure 8-33.

usual desire for declaring a width on floated textelements in any case, but the specification does notrequire that a width bedeclared in order to make a text element float successfully. InternetExplorer 4.x for Windows does.

Also, you must have the final version of Explorer 4.x for this towork -- so if you're still using a preview release,you'll need to upgrade it, which is probably a good ideaanyway. (Thanks to Howard Marvel for discovering and sharing this off, there is the ability to create a selector that matches anyelement with the specified attribute. For example, you can match allanchors with a NAME attribute, or allIMG elements with a BORDERattribute, or all elements that have a class of some type:

A[name] {color: purple;}      /* colors any NAME anchor purple */IMG[border] {border-color: blue;}  /* sets blue border for any bordered IMG */[class] {color: red;}        /* sets any classed element red */

In none of these situations does it matter what value is assigned to