Skip Navigation
Jack Baskin School of EngineeringUC Santa Cruz

Guidelines for reviewing Web pages on SOE sites

Previewing Documents

  1. All pages need to include the standard header and footer and should be based on the SOE templates.
  2. Make sure links clearly identify the page they're linked to. For example, a link titled "Undergraduate Advising" shouldn't link to the page about "Disqualification Policy". It should link to the undergraduate advising homepage.
  3. Map page titles to URL structure. For example, this page is <title>'d:

    SOE Web review guidelines - SOE Web site - Jack Baskin School of Engineering, UC Santa Cruz

    ...to match the URL /site/guidelines.html. "SOE Web review guidelines" refers to this page; "SOE Web site" refers to the "/site/" directory; "Jack Baskin..." refers to the SOE homepage (at "/"). Separate each title section with two spaces around a dash (" - "). The page title is in the "Title:" field at the top of each page in Dreamweaver.
  4. Include a short descriptive document title that describes the contents. The document title appears directly below the blue global navigation bar. This should appear in <h1> or <h2> tags and have a class of "main_title" (see the "Guidelines for reviewing Web pages on SOE sites" title above).
  5. Set the "Section Title" to (1) the title of this section of the Web site (usually the title of the index.html page), or (2) the directory above it if it is the index.html page. Then link this Section Title to the index.html page, or the directory above. See the examples at (1) /programs/ams and (2) /programs.
  6. Pages about the same topic should be within the same folder . The main page within each directory should have the filename "index.html". This file is the default page when the URL ends with a directory. For example, /advising/undergraduate/ and /advising/undergraduate/index.html are the same page.
  7. Use consistent, short, and immediately identifiable labels for links. All links should fit within the side bar.
  8. Use server-side include files (for example, "nav.ssi") for content or links shared by more than one page.
  9. Include an email link for the person responsible for the page at the bottom of each page. This link and contact info should be in a server-side include file. An email link looks like "mailto: ".
  10. When possible, post HTML pages instead of PDF documents. Not all browsers support displaying PDF documents, or don't do so consistently.