Milestone 2 - Static Site

Instructions

Work with your team to create the beginning of your dynamic web application prototype as a static site. Follow the design you proposed in Milestone 1, incorporating the feedback you’ve received and lessons you’ve learned since then.

Requirements

2.1.

You must use the git repository your professor created for this project.

2.2.

You must publish the site

2.3.

Your site must include a page called report.html that is accessible from URL root of your site, and this report.html must include at least an ordered list where you briefly explain how your site meets all of these requirements (or if you aren't going to meet a requirement, you explicitly write that you did not meet that requirement). i.e. first item in your list should say like

1. this is the url to our github repo which is shared with each other and the prof: http://github.com/...
2. this is the url to our deployed application where anyone could try our app: http://example.github.io/...
...
13. Right now we are thinking that the 2 APIs we will use are https://developers.giphy.com/docs/api#quick-start-guide and https://developer.spotify.com/documentation/web-api/reference

2.4

Your site must support distinct layouts for large and small screens using media queries. Use comments to note where you completed this activity. You may do this in a variety of ways. Consider using this to control images or switching blocks between rows (for large screens) and columns (for small).

2.5

Your site must contain at least five separate pages, each having a meaningful purpose. One of the files should be named index.html. Your pages must link to each other in a logical and meaningful flow.

2.6

Your site must include some sort of header.

2.7

Your site must include some sort of navigation links.

2.8

Your site must include images, and their alt attributes must adequately describe the image content to users of screen readers, users with images disabled, and webcrawlers.

2.9

Each page and stylesheet of your site must validate without any warnings or errors using the Nu Validator and WAVE Web Accessibility Evaluator.

2.10

Your site must use at least two different font faces. Headings are often rendered in a sans-serif font, and paragraph copy in a serif font.

2.11

Your site must include at least one form. The form need not do anything at this point in your learning, but it must be present and it must use built-in content verification. Like all content, it must be neatly aligned.

2.12

Your site must include links to external sites.

2.13

You have some ideas (minimum 2) about network requests you might make to support the next milestone's interactivity.