tl;dr Produce a professional, responsive, and polished version of your Apple Harvest Festival website by employing the user-centered design process.
Project Document Summary:
Coding Resources:
| Submissions | Deadline | Slip Day Deadline | Credit |
|---|---|---|---|
| Milestone 1 (p2m1) | Wed 3/6, 11:59pm | Thu 3/7, 11:59pm | 36 points (correctness) |
| Milestone 2 (p2m2) | Wed 3/13, 11:59pm | Thu 3/14, 11:59pm | 52 points (correctness) |
| Final Submission (p2fin) | Wed 3/20, 11:59pm | Thu 3/21, 11:59pm | 100 points(correctness) |
Before you begin your Final Submission, revise your project based on your Milestone 2 feedback.
When revising your plan in the design journey, don’t delete your “old” answers. Remember, we want to see your design’s journey; you are graded on your design process. If you later change your mind, keep the “old” answer and then add a new one below it explaining why you changed your mind.
When working for a client, you’ll need to check their requirements frequently to ensure you’re meeting their expectations. You don’t want to spend weeks working on something only to discover at the last minute that what you’ve been working on doesn’t meet their requirements.
Please go back and re-read the project overview and project requirements.
Code your complete design. Your site should have all its content; there should be no placeholder content.
Your finished site should be fully responsive between narrow and wide screens. Use responsive CSS (media queries) to produce your responsive website. You may not create separate files (i.e. HTML and CSS) for mobile and desktop versions of your site. You may not just set the width of all elements to 100% to make it “responsive.”
When you’ve finished your site and all content is included, delete the “m-content” folder.
User test your site with at least 2 distinct users.
You will need to develop a test plan with at least 2 tasks for user testing. Develop your task plan in the design journey.
Your first step is to find appropriate test users. It is best to invite users that belong to your audience, otherwise, it is difficult to say your testing is valid for your audience. Please do not ask your friends and family to be your participants. Friends/Family do not make good user test subjects because they know you and are less likely to provide completely honest feedback.
Once you have found your testers, you should begin doing user testing with them focusing on:
While testing, take thorough notes on what issues each user had with each task and what worked well. Include your user testing notes in the design journey.
Reflect on the issues discovered during testing and how you would resolve the usability issues with your design. You don’t need to revise your design, just reflect on what you would do to address the usability issues.
Provide explanations for the changes that you made in the design-journey.md.
Once you’ve finished the final site, take a moment and explain your final site’s design in the design journey.
You wouldn’t hand off the final version of a site to a very important client without checking that you’ve met all the client’s requirements first. Professionalism is important. Check your final website against the project’s requirements. Remember: a client won’t provide you with a rubric. Instead, you need to evaluate work using the requirements.
Tip: Put a check mark next to every requirement in the write-up as you check your site.
Do not wait to start this milestone! CSS can be surprisingly difficult and often renders differently in different browsers. CSS can take a surprisingly long time to fiddle, and visual design takes a while; start early.
Be a thoughtful critic of your own work. Learning to evaluate your own work is a learning outcome of this course. Don’t assume if you didn’t get a comment about something in earlier milestone feedback that everything is great. Don’t assume we’ll catch all problems every time.
Make sure your design-journey.md is thoughtful and well done. Students sometime only focus on the website and forget that thinking through your design is equally, if not more, important.
Getting more feedback from more people – your peers, TAs in office hours, people you’re designing the site for, both along the way and through informal user testing – will help you improve your work quickly.
Follow the code copying and citation polices in the syllabus. Not acknowledging the source is passing ideas and work off as your own; this is plagiarism and kills grades (in school) and reputations (everywhere). Borrowing and adapting is totally in the spirit of the web design community, but you have to give credit where it is due.
Stage, commit and push all changed files in your Git repository to GitHub. (All commits must reside on the main branch.)
Then, complete the submission form.
Note: All files must be in the location specified in this document for credit; our grading process cannot reliably locate your work in other locations.