Hi ASU Web Community,

We need your feedback! As you probably are already aware, the ASU site will be adopting a new header and footer. Thanks again to everyone for their input concerning the revisions. The input greatly influenced the final design which has been approved by the Executive Leadership and the Web Editorial Board.

Next steps…
The Rev 2.0 Template Implementation Team is now developing code and documentation for the new look and will be making it available to the community at http://template.asu.edu when it is completed on April 15th. It will be up to you all to apply the code to the pages you are responsible for by the end of May (for core pages) or by January 2009 (for departments and colleges). Are these dates feasible?

See the ASU Core Webpages spreadsheet for a list of what is considered to be part of the ASU core and identify if you are listed as a lead developer for any of the web pages. If you see any inaccuracies on this document, please let us know. The spreadsheet does not include college and department specific web pages. If you are responsible for a college or department related site that is not on the spreadsheet or know someone that is, please respond with the responsible person's name, college or department, and cooresponding url(s) to help us build out spreadsheet.

We would like to anticipate your needs to ensure that applying the template to your existing code is as easy as possible. The basic template details are posted below.

The template versions that we will be providing are:

1. xhtml includes
2. static html/css template
3. the updated ASU Zen theme for Drupal 5.x Sites

The template versions will include:

1. Both a gold version of the template and a maroon version of the template. Core sites are expected to use the gold version. Departments and colleges can choose what version to use.
2. A template version that has the Sign in / Sign out option as well as a template version that does not have a way to authenticate.
3. A template version with radio search buttons and one without radio search buttons (see Slide 4 of the Google doc presentation). Core sites should not use the radio buttons. Departments and colleges can choose to use the radio buttons if they desire.
4 . Endorsed logos that will be provided as png versions and will be hosted on UTO servers to reference in the code. Endorsed logos should link to the college / department home not the ASU home page.
5 . The header and footer in liquid form. Both core sites as well as colleges and departments should use it in this form. The content area can either be liquid or fixed, however. We will provide an example of how to make a fixed width layout for the content area.
6 . The same style names as the previous template versions.
7 . The coding elements in a particular order in order to be accessible by screen readers and other devices.

Template implementation suggestions:

1. For sites on afs we suggest that includes are used if possible. For sites on servers not on afs or UTO hosting, we recommend that you setup the afs client on your web servers in order to pull the includes on UTO afs space. Directions for how to set up the afs client to be posted on the web community shortly…

Please respond with anything that you see as overlooked that will prevent you from easily implementing the new header and footer to your pages. Any suggestions for how we can make this process easier for you are greatly appreciated.

Stay tuned for further details about code availability and documentation. Thanks for continuing to be a part of this university-wide effort!

The Rev2.0 Design Team