The data for each card should include:
Name
A single picture for the listing
A button that, when clicked, shows more details for the listing at a new route

• Area
• Area Details
• Listings

Complete all testing for the components

the user should be introduced to a welcome form asking for:

• the user’s name
• their email
• and a purpose/goal for using this listing app.
• an error message should appear
• all inputs must be filled in

• Achieve 100% on accessibility audit
• Make site completely accessible via keyboard

I attempted to make the site completely accessible via keyboard, but favorites cannot be selected using the tab button.

Upon signing in, the user should be redirected to /areas where they should see a breakdown of the various areas of Denver.
Each area should have all pertinent information listed, including:
shortname of the area (ex. RiNo)
name of the area (ex. River North)
a description of the area
There should a button on each card to view listings for a specific area
NOTE: This button doesn’t need to have any functionality in this iteration. Details on what the button does will be outlined in future iterations!
The user’s profile data should be displayed with their name, a short greeting dependent on their purpose for using the listing app
A Sign Out button should also be available, logging the user out and redirecting them back to the root route, /.

When a user clicks on the View Listings, the user should then be redirected to /areas/:area_id/listings/.
NOTE: Be careful on how to structure this route. The parts of the route that are dynamic (ex: /:area_id) should not actually include a colon - it is simply to show that this part of the route should change. An example of what a completed route would look like could be: /areas/66

Complete testing for all of the aforementioned components

When a user clicks a specific listing, they should be redirected to /areas/:area_id/listings/:listing_id and get a more detailed breakdown of a specific listing. This card/view should include:
Address
Number of Bedrooms
Number of Bathrooms
Cost per Night
All pictures of the listing
Unique features of the listing
A button to “Favorite” the listing
Note: User should still see their profile info and be able to log out.

Complete testing of App.js, AreaContainer, and Login.js

• Login.js
• App.js
• AreaContainer.js

Create the App.js file, which should contain:

• state
• methods (possibly sign out method)
• a fetch request within componentDidMount?
• a render method that uses routing
• an import of BrowserRouter

There should be a button on each card to save it to Favorites.
There should also be a button that when clicked, links the user to the /favorites route and displays only the favorited cards.
This button should also show the count of favorited items in the button text.
Users should be able to unfavorite a card both on the relevant route (/areas/:area_id/:listing_id) as well as the /favorites route.
If there are no favorites, there should be a message indicating that there are no favorites.

The data for each card should include:
Name
A single picture for the listing
A button that, when clicked, shows more details for the listing at a new route

• Update styling on the individual listings page
• change font size and type on navbar
• update font in area container to match overall Roboto font

Create README

Slack

Incorporate an interactive map into your app!
Implement a map that shows where all of the listings are located when a user goes to the /areas/:area_id route for a specific listing area.
When a user clicks on a listing marker on the map, you should display an info box that includes:
An image of the listing
A link to the specific listing pages

Add images to each individual area (to show up on area page)

Testing for the FavoritesContainer and IndividualFavorites

Create a web mockup using figma of all site pages

Importing SASS into React

We ran into issues implementing the apiCalls file with our tests. Unfortunately, this broke some of our existing integration tests and prevented us from completing the rest of our integration tests.