Rod Library Web Site Redesign Staff Informational Session and Discussion November 30, 2007

Goal of Redesign Project Address the overall look of our site, accessibility, and usability Strong navigation throughout site Update look Ensure pages are accessible by those with visual, auditory, physical, speech, cognitive, and neurological impairments

Address the overall look of our site, accessibility, and usability

Strong navigation throughout site

Update look

Ensure pages are accessible by those with visual, auditory, physical, speech, cognitive, and neurological impairments

Why do a redesign? Wide variety of styles Inconsistent or non-existent navigation Older styled pages Content that has not been reviewed or updated recently

Wide variety of styles

Inconsistent or non-existent navigation

Older styled pages

Content that has not been reviewed or updated recently

Unified site-wide design Improve navigation More cohesive style Site will be looked upon as an even more reliable source for information Examples of unified designs: Ohio University Libraries Illinois State University, Milner Library Unified designs also present on top commercial web sites such as YouTube , Wikipedia , Nolo , Dell

Unified site-wide design

Improve navigation

More cohesive style

Site will be looked upon as an even more reliable source for information

Examples of unified designs:

Ohio University Libraries

Illinois State University, Milner Library

Unified designs also present on top commercial web sites such as YouTube , Wikipedia , Nolo , Dell

Stylesheets will be used to control the look and style of the pages Web and accessibility standards will be followed Templates will be employed Web content management system will be used to manage our web content

Stylesheets will be used to control the look and style of the pages

Web and accessibility standards will be followed

Templates will be employed

Web content management system will be used to manage our web content

Which pages will convert to new look? All pages in the libedit directory initially Library applications will be addressed individually later on Faculty and staff pages which are linked to from the library’s public Web site but are stored on the UNI server will be reviewed

All pages in the libedit directory initially

Library applications will be addressed individually later on

Faculty and staff pages which are linked to from the library’s public Web site but are stored on the UNI server will be reviewed

Templates Basic look will be created with staff and user input Main header and footer with basic navigation on every page Subpages will have sub-menus for navigation and can have a sub-header that defines the section of the site Different content options for laying out content

Basic look will be created with staff and user input

Main header and footer with basic navigation on every page

Subpages will have sub-menus for navigation and can have a sub-header that defines the section of the site

Different content options for laying out content

Why should we use templates? Content editors will not have to learn or use HTML code to write their pages Staff will have more time to spend on their content since they will not have to fight html code Design of our site can be changed easily to meet future demands Site will be easier to maintain overall

Content editors will not have to learn or use HTML code to write their pages

Staff will have more time to spend on their content since they will not have to fight html code

Design of our site can be changed easily to meet future demands

Site will be easier to maintain overall

What is a Web content management system (CMS)? Software application used for the creation, reviewing, updating, publishing, and storage of Web content Assists with managing the structure of a Web site as well as the look of the site

Software application used for the creation, reviewing, updating, publishing, and storage of Web content

Assists with managing the structure of a Web site as well as the look of the site

Benefits of a CMS Greater consistency across our site Site navigation will be improved and monitored more easily Content can be created once and reused or duplicated across the site Links can be verified or checked more easily

Greater consistency across our site

Site navigation will be improved and monitored more easily

Content can be created once and reused or duplicated across the site

Links can be verified or checked more easily

Benefits of a CMS Would help us manage our content more effectively Option of adding dynamic pages to our site; pages which the web server builds on the fly based on user clicks (it would work similar to what you find on Amazon.com) Easier to make global updates to content and links More effective management of templates

Would help us manage our content more effectively

Option of adding dynamic pages to our site; pages which the web server builds on the fly based on user clicks (it would work similar to what you find on Amazon.com)

Easier to make global updates to content and links

More effective management of templates

How will a CMS and templates change the way staff work? Given access to the pages for which they are responsible Choose template based on content Apply some styles to content such as headings and lists; other styles controlled by stylesheet Use a WYSIWYG interface to make changes No fighting the code

Given access to the pages for which they are responsible

Choose template based on content

Apply some styles to content such as headings and lists; other styles controlled by stylesheet

Use a WYSIWYG interface to make changes

No fighting the code

Questions so far on . . . General redesign Use of templates Use of Web content management system Way staff will work with their content

General redesign

Use of templates

Use of Web content management system

Way staff will work with their content

What has been happening so far? One usability test on entire site Planning for second usability test on electronic resource access Review of two Web content management systems, Drupal and Joomla Planning for review of content Content editors have begun reviewing their content

One usability test on entire site

Planning for second usability test on electronic resource access

Review of two Web content management systems, Drupal and Joomla

Planning for review of content

Content editors have begun reviewing their content

Expectations for Remainder of Process Second usability test in January Card sorting in early spring Identify a Web content management system Assist content editors in reviewing their files, file structure, and content as needed

Second usability test in January

Card sorting in early spring

Identify a Web content management system

Assist content editors in reviewing their files, file structure, and content as needed

Expectations for Remainder of Process Create mock ups of designs Gather input and test Make changes Repeat process as needed

Create mock ups of designs

Gather input and test

Make changes

Repeat process as needed

Questions about . . . Remaining work? Guidelines for reviewing content?

Remaining work?

Guidelines for reviewing content?