1. Hannah Leland
2. Andreas Vassilakos

* Conduct a task analysis for creating a user-centered design
* Select 3 page of the website to redo. Two content pages and one process page. The process page should be a html form page. Like a sign up page or a purchase page. One content page should be the home page.
* Apply design principles including color/material, typography, accessible media, and grid-based design.
* Execute a progressively enhanced, touch-friendly, mobile-first responsive design focused on system users and tasks.
* Write informative text content; catch error conditions and guide users accordingly.
* Experiment with design and interaction patterns for pleasing user experience.
* Engage in agile, iterative web design and development within a team-based work-flow on GitHub, via pull requests and code reviews.

1. Lab 5 Whole team: Create a group or join a group on Basecamp Project 2: Group Sign Up. Groups should be 3 people each. Group names should be creative. Each group member should list their GitHub username and one team member should be chosen to initiate lab 5.
2. First Deliverable: Task Analysis Whole Team: Create a Basecamp post describing your work in progress. Title the post with your team name and project number (example: Team Wonder Women - Project 2). Your post should include the full names of all team members, and a screen-by-screen task analysis of your redesign. Use screen shots and simple text to explain your plan of action.
3. Second Deliverable: Whole Team: Update your project 2 Basecamp post with the URL to your group GitHub repository, live link (GitHub pages), and two questions eliciting feedback from fellow students.
4. Comments: Individual: Give constructive comments to help at least three other teams.
5. Final Deliverable:Whole Team: Revise your team Basecamp post under Project 2 to add links to each member's individual fork of the group GitHub repository. Individual forks should include README.md files with following:

* All source files in UTF-8/Unicode character encoding.
* No code-generators like WYSIWYGs, Bootstrap, or other off-the-shelf frameworks
* HTML, CSS, and JavaScript files should both be indented with 2 spaces per level of indent; indent all CSS style rules inside the declaring block, and further indent all rules and blocks inside your media queries.
* Must pass HTML and CSS validators!

1. Only structural, semantic uses of HTML elements and attributes. Absolutely no table markup, break tags, or any other use of HTML to achieve a particular page layout.
2. Valid HTML form elements, written in conjunction with <label> tags and the for attribute.
3. Semantically structured text-based HTML content to accompany any media elements (image, audio, video)

1. CSS file should open with a set of reset styles. Meyers, and the Form section of Normalize.
2. Use at least two min-width media queries to enhance your mobile-first styles for larger screens.

1. JavaScript that throws no uncaught errors and is loaded unobtrusively (no JavaScript event attributes in your HTML, in other words; attach events to any elements requiring interaction).
2. JavaScript that uses only asynchronous methods and callbacks

1. Whole team: A shared team Git repository with frequent commits from each team member and meaningful commit messages that accurately reflect each set of changes.
2. Each team member: An individual Git repository with feature branches, frequent commits, and meaningful commit messages that accurately reflect each set of changes that you make, including experimental work that you ultimately might not push upstream to the shared group repository.
3. All GitHub repositories (team and individual) must contain only the files and commits from this project.