This Style Guide explains the markup and design requirements for web projects, along with various standards and best practices.
When you create your data using an XML editor (that you can write), you can not only input the content of your data, but also define the structural relationships that exist inside your data. By allowing you to define your own tags and create the proper structural relationships in your information (with a DTD), you can use any XML parser to check the validity and integrity of the data stored in your XML documents. This makes it very easy to validate the structure and content of your information when you use XML. Without XML, you could also provide this validation feature at the expense of developing the code to this yourself. XML is a great time saver because most of the features that are available in XML are used by most programmers when working on most projects.
By using XML and Java, you can quickly create and use information that is properly structured and valid. By using (or creating) DTDs and storing your information in XML documents, you have a cross-platform and language independent data validation mechanism (for free) in all your projects!
You might use XML to define file formats to store information that is generated and used by your applications. This is another use of the structured nature of XML. The only limitation is that binary information can't be embedded in the body of XML documents. For example, if you wrote a word processor in Java, you might choose to save your word processor documents to an XML (actually your ApplicationML) file. If you use a DTD then your word processor would also get input file format validation as a feature for free. There are many other advantages to using XML and a file storage format for your applications which will be illustrated later in the chapter.
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.