This page provides an HTML implementation of the 2003-2009 standard "official_pages1" CommonSpot template's look and feel for use outside of CommonSpot.

This is an obsolescent design.

For new projects, please consider using one of the three following variations on the current design:

• the CSS-free implementation of the 2009-? CSS-based CommonSpot template's look and feel for use outside of CommonSpot, using the standard design width of 960 pixels.

• the CSS-free implementation of the 2009-? CSS-based CommonSpot template's look and feel for use outside of CommonSpot, modified to use a design width of 672 pixels, instead of 960 pixels, so that printed copies will be easier to read.

• the CSS-based implementation of the 2009-? CSS-based CommonSpot template's look and feel for use outside of CommonSpot, using the standard design width of 960 pixels.

None of these four designs should be used for personal, student organization, or other unofficial web pages.

The green "sitewide nav bar" (above, just below the header) is an optional feature. It will work on any web page that the world sees at http://www.ohio.edu/ (e.g., when published on the static-page Front Door server), but it will not work for web pages at other locations, such as during testing from your disk drive, or when published from a departmental server. If you decide not to include it, remove the table that contains it, and also remove the SCRIPT tag (which mentions "HM_Loader.js") immediately before it.

In the HTML for this page, each instance of "672" may be replaced by any larger number of pixels (e.g., "760") or by "100%". If the sitewide nav bar is removed, "570" or larger will work. Any value larger than 672 will cause portrait-mode-printed copies of the pages to be shrunk to fit, for some combinations of platform, browser, and printer, risking readability problems.

The images in the header will not load properly when you view them from your disk drive if your computer is not connected to the internet, but they will display correctly from any location on any server. If you routinely need to work offline and your pages will be on the Front Door server, then you could replace every instance of 'src="http://www.ohio.edu/www/' with 'src="../www/' or 'src="../../www/' (and so on: the number of '../' cycles matching the depth of your location on the Front Door server). Then you need only store copies of those graphics on your computer at the corresponding location, as discussed in the static-page author's guide.

The "boilerplate" section, below, identifying the author, URL (in the printed version), and date, is not part of the standard design, but may be added as the final part of the page-specific content. Identifying the people responsible for a page raises the odds that people will contact you with suggestions for improvements; including the date of revision as part of the visible text of the page is particularly appropriate if the page contains instructions for others to follow, or if the information is likely to change; including the full URL of the page is likely only of value in cases where someone has printed the page, and their browser has not automatically included the full URL in the top or bottom margin (some browsers will "fit" a long URL by leaving out the middle or truncating it, rendering it useless), so the "PageURL" style in the HEAD of the page, and the SPAN tag in the footer conceal it during on-screen viewing. If you expect your pages to be printed, and don't use the boilerplate, it is probably wise to provide some full-width item, perhaps a Horizontal Rule, immediately above the footer, because most browsers will not print the footer's background or border, leaving the left and right sides unconnected.

Feel free to "view source," or to "save page as..." in order to copy the HTML of this page to your disk drive to use as a starting point. If you do, be sure to change both the visible text and the HREF for the e-mail link at the bottom-left! We do suggest leaving the pre-loading of the e-mail subject in the code, but you should change it to specify your subsite. We suggest using a departmental e-mail address, rather than a personal e-mail address, to avoid having to update every web page following a staffing transition or during a vacation.

The Google Analytics code will only generate useful information for you if you let us know that it is in use for your subsite. Please leave it exactly as it is in this page, and place it at the end (just before the </HTML> tag), so that if the Google server is slow for some reason, your page will still be fully displayed by the browser without delay.