Propose a redesign for a library web site, grounded in an analysis of its users, goals, strengths, and weaknesses. Prototype your proposal. Deliver both your proposal and your prototypes as web pages.
This is a group project; your group can divide the labor in any way that seems fair to you. Your group should have 4-ish people.
Why do we do this?
A library web site redesign is a common, and daunting, real-world task which relies on all the skills we've discussed in this course. Proposing one will let you practice those skills (as a bonus, these skills are applicable all over web work, not just in the redesign context). Getting your feet wet with the redesign process now will also make it more approachable should you be involved in one professionally.
Due May 16.
- Your report, analyzing the existing site and proposing changes;
- Your protoype, consisting of two pages: a home page and an internal page, exemplifying the changes you are proposing.
Both of these should be web pages: HTML, plus whatever CSS and JS you need to demonstrate your vision. Deploy these, whether to UW My WebSpace or externally, and provide the links in the Deliverables thread of the Final Project forum at Learn@UW.
- What is the site you're redesigning?
- Who are the site's users? (Think in terms of demographics, but also personas: what do people want to do here?)
- What are the site's goals? (What content does it - or should it - provide access to; what interactions does it - or should it - facilitate.)
- How should the site be organized to achieve those goals?
- Is it usable? As part of your analysis, actually test the usability of a component, following the examples this term of quick, cheap testing.
- Is it accessible? As part of your analysis, test its accessibility with one of the tools we've discussed this semester.
- What does the site do particularly well or badly?
- What are your recommendations?
You may organize this content in any way you like, so long as it reflects good use of HTML organizational elements (e.g. headers) and best practices for web writing as described in Krug (e.g. be concise).
Your recommendations should be clearly grounded in evidence and in concepts you've learned this term, and should address the issues of users, goals, strengths, weaknesses, etc. covered elsewhere in your report.
Your prototype should clearly demonstrate your recommendations.
- If your prototype has a catalog search, show me exactly what that should look like, but I don't expect it to perform searches.
- Your prototype's navigation should reflect the areas you think the redesigned site should have, but the links need not work as the linked pages may not exist.
Both your report and your prototype are web sites, and as such should...
- Validate for XHTML or HTML5, using validator.w3.org.
- Be without errors per WAVE. It's okay if there are alerts (though I will give you a bonus point if there are no alerts).
- Be responsively designed (for phone/tablet/desktop).