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)
Another example is web enabling legacy systems. It is very feasible to create a Java web ennoblement application server that simply uses the services provided by the underlying legacy system. Instead of rewriting the legacy system, if the system can be made to communicate results and parameters through XML, the new and old system can work together without throwing away a company's investment in the legacy system.
By making the W3C the keeper of the XML standard, it ensures that no one vendor should be able to cause interoperability problems to occur between systems that use the open standard. This should be reassuring to most companies making an investment in this technology, by being vendor neutral, this solution proposes to keep even small companies out of reach of big companies choosing to change the standards on them. For example, if a big company chooses to change the platform at its whim, then most other companies relying on that platform suffer. By keeping all data in XML and using XML in communications protocols, companies can maximize the lifetime of their investment in their products and solutions.
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.