Guidelines for Custom Templates

The following guidelines are to be used on custom templates that have been pre-approved by University Web Services. Changes should not be made to department templates.

Websites using department templates should follow default styling and should not need to override styling unless approved by University Web Services.

Sites that use custom or wide templates as defined by University Web Services should also observe the following guidelines:

General Guidelines

  • Custom pages should only use the Foundation framework, grid system and classes. If the template references global.css, header.php, template.php, or footer.php, Foundation must be used.
  • Rems should be the primary unit of choice unless in some cases where px may be acceptable. Ems should not be used.
  • HTML should follow university standards for accessibility/508 compliance.
  • CSS should not be used to remove elements from displaying on page.


  • Heading 1 should only be used by the page title and is the only one allowed to have the Adobe Garamond font stack.
  • All subsequent headings should only use the Myriad Pro san-serif font stack.
  • Headings should not be bolded manually and should inherit default font styling or use the .bolder classes.


  • Images with text should not be used. Instead, HTML and CSS can be used to have text placed on top of an image and should follow the image module HTML structure.
  • Myriad Pro must be used if text is over images. Adobe Garamond Pro and Myriad Pro Condensed is not allowed.
  • Left and Bottom padding should be equal, starting with 0.5rem or 1rem.
  • Images should not be used in place of headings.

Other Do's and Dont's

  • Text should not be centered in located in the body copy area of a page.
  • Development pages need to be set to only publish to so that it does not appear on our live websites or be indexed by search engines.