Had been using same site since 1995.- lots of out of date content and design, every site out doing their own thing - no unifying navigation, users had to reorient themselves every time they would hit different section of the site.
used a consultant team to review current site - have a new team reporting directly to president - web communication department was born
Redesign and rearchitect the site
challenges - buy-in and keeping project interest
campus partnerships
new components
good design
keep campus (esp stakeholders) in the know
Migration -
campus education
screen reader available in web comm office
google analytics - use for content and design decisions (screen res, etc)
note: look at museum of art
lessons learned
can we do "fake" rss with reference paragraph?
used a consultant team to review current site - have a new team reporting directly to president - web communication department was born
Redesign and rearchitect the site
challenges - buy-in and keeping project interest
campus partnerships
new components
good design
keep campus (esp stakeholders) in the know
Migration -
- prioritized sites
- migration should improve current sites
- info arcitecture
- analytics
- usability
- 10 templates with minor variations between each
- new design or modify and fit within wireframe
- department or Partner agency can do it themselves
- predesigned templates
- text image
- dynamic flash -create movement/interest in site without having to do it themselves
- tab block
- polling
- comment
- rss output
- photo gallery - create thumbnails and set up gallery from media library
- profile gallery (alumni)
This would be great for subject specialists/public services - calendar - doing some great stuff with calendaring with different levels - can push up events to different department levels all the way up to campus-wide
- forced alt text in media library
campus education
screen reader available in web comm office
google analytics - use for content and design decisions (screen res, etc)
note: look at museum of art
lessons learned
- identifying requirements
- design vs development
- going live w/out redundancy ( any probs give bad pr to all users)
- lacking define web requirements
- buy in, interest
- creating and maintaining achievable schedule
- documentation - before migrating - understanding responsibilities - bad design and bad content ae not allowed to migrate
- usability testing - new issues, confirm decisions
- system free to campus - building functionality with all departments
- relationship with Day
can we do "fake" rss with reference paragraph?
Leave a comment