Friday 31st of March 2017 02:25:43 AM
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
- 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
there is an important warning to be made. You're probably awarethat browsers ignore tags they don't recognize; for example, ifa web page contains a BLOOPER tag, browsers willcompletely ignore the tag because it isn't a tag theyrecognize.
The same will be true with style sheets. If a browser does notrecognize <STYLE> and</STYLE>, it will ignore them altogether.However, the declarations within those tags will
- 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.
Let's consider once again a floated image which is floated tothe left, and which has left and top margins of-15px . This image is placed inside aDIV which has no padding, borders, or margins. Theresult will be as shown in Figure 8-42.
Figure 8-42. Floating with negative margins
Contrary to appearances, this does not technically violate therestrictions on floated elements being placed outside their parent
There's a downside: as of this writing, web browsers
don't get this fixed alignment right, so this example was just
an interesting theoretical exercise.
6.2.6. Bringing It All Together
Just like with the font properties,
XML enables interoperability
All of the advantages of XML outlined so far all make interoperability possible. This is one of the most important requirements for XML, to enable disparate systems to be able to share information easily.
By taking the lowest common denominator approach, by being web enabled, protocol independent, network independent, platform independent and extensible, XML makes it possible for new systems and old systems (that are all different) to communicate with each other. Encoding information in plain text with tags is better than using propietary and platform dependent binary formats.
spans the width of the parent, and so does the background. The actual
content doesn't flow all the way across its own content area in
order to avoid being obscured behind the floating element.
220.127.116.11. Negative margins
As was discussed in the previous chapter,
negative margins can cause floated elements to move outside of their
parent elements. This seems to be in direct contradiction to the
rules explained earlier, but it isn't. In the same way that
There are many uses forcolor, of course, the most basic of which is toreplace the BODY attributesTEXT, LINK ,ALINK , and VLINK. Inconjunction with the anchor pseudo-classes, colorcan replace these BODY attributes outright. Thefirst line in the following example can be rewritten with thesubsequent CSS, and either will have the result depicted in Figure 6-3: