These pages are designed to match the look and feel of the main Cal Poly Pomona pages, for use by other parts of the university. The links below are to example pages, and to the current Cal Poly Pomona pages that they emulate.
All the files are available in a zip archive, which also includes the images and stylesheets all properly linked to be placed at the top level of your site.
A detailed tutorial is available in ehelp.
These templates will appear somewhat different in Dreamweaver CS3 or Dreamweaver 8 than they do in a browser. They will appear very different in Dreamweaver MX 2004, and may not be usable in previous versions. Don't try to fix the appearance in Dreamweaver until you have seen the same problem in a browser.
The templates use no layout tables or <font> tags, and are designed to be used with little additional markup. The <h1> tag is used for the page heading above and for the column heading at right (the gold letters above are the result of applying the CSS class .goldletter). The <h2> tag provides the gray-background subheads, and the <h3> tag is below:
Lists are used for navigation in the top horizontal menu, the left and right navigation, and the footer navigation. In all cases, the bullets are eliminated and margins are adjusted, and in the horizontal navigation at top and bottom, the list items are set to display in-line. List navigation is much more accessible to disabled users that simple columns of text—some screen readers will tell the user how many items are in the list.
In the central column, bullets are retained, but if you would like the list style of the CPP home pages, you may change the stylesheet content_area.css to activate those styles and deactivate the current styles (using comment strings).
The Dreamweaver "indent" button doesn't really indent, but rather creates a <blockquote>, which usually appears indented in a graphical browser. The style sheets define an appearance for <blockquote> that is different from paragraph text, so this misuse of the "indent" button will have a different effect. Also, the <font> tag is deprecated, and chrome.css redefines it to remind you of that.
Each template has a page_heading region in addition to the content region. Because the editable part is inside the <h1> tag, Dreamweaver will give a warning when you save a template. You can ignore it.
In addition, the templates with navigation columns have editable regions there as well, to allow you to turn off each page's link to itself. If an editable region will remain unchanged in your implementation, you can remove it.
Remember that you can change non-editable regions in the template, especially the footer, which currently has the links of the CPP home pages.
Each template links separate screen and print stylesheets. The screen stylesheet "imports" several additional stylesheets (by importing rather than linking, Netscape 4 gets unstyled content, rather than messing up the page with its broken style implementation).
The eight page types each have a separate linked stylesheet (the second in each case is for the version with a top horizontal menu):
Each imports a stylesheet with its specific layout:
Each also imports these stylesheets. Two are used in every page type:
The styles that have left columns use leftnav.css, and the styles that have right columns use searchcolumn.css. Finally, one of two style sheets is used depending on whether or not there is a top horizontal menu:
There is also a print stylesheet, print.css. It makes the navigation areas invisible and sets the width of the contents to auto, so that they will print without being cut off.
These pages have been tested in a number of modern browsers, and work acceptably in all (Netscape 4 gets unstyled content, older versions of Opera have some formatting problems, IE 4 is ugly but usable, and IE 5 for Macintosh has some minor problems)). If you have problems with a specific browser, please contact webteam@csupomona.edu.
It is important to make sure that you don't put a too-wide item (such as an image) into a column. These pages will break in a different way than layout-table pages when the width is forced to increase.
Most of these changes are to aid template implementers in proper use of the templates. None of them change functionality of the templates.
Version 1, version 2, version 3.0, version 3.5, and version 4.0 templates are deprecated, but still available for repairs and nostalgia