You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+17-22Lines changed: 17 additions & 22 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -22,36 +22,31 @@ Frontend: React.js
22
22
Backend: PostgreSQL, Express.js, Node.js
23
23
24
24
## Features
25
-
1. Sneaker World is programmed using Express and and ReacT and includes dynamic routes.
26
-
2. The entire application is deployed using Railway
25
+
1. Sneaker World is programmed using Express and and React and includes dynamic routes.
26
+
2. The entire application is deployed using Railway.
27
27
28
-
### Backend
29
-
30
-
Sneaker World's backend will have at least one of each of the following database relationship in Postgres:
31
-
3. A user can select multiple sneakers to add to their cart (one-to-many)
32
-
4. Multiple sneakers can be joined with multiple categories such as: casual, running, cross-training, etc. (many-to-many)
33
-
Sneaker World implements a well-designed RESTful API that:
34
-
5. Responds to GET, POST, PATCH, and DELETE requests in order to allow for cart and orders to be properly deleted.
35
-
6. Implements proper naming conventions for routes.
36
-
The web app implements the ability to reset the database to its default state in order to create a clean slate and create a consistent UX.
28
+
### Backend Features
29
+
3. A user can select multiple sneakers to add to their cart (one-to-many database relationship in Postgres).<br>
30
+
4. Multiple sneakers can be joined with multiple categories such as: casual, running, cross-training, etc. (many-to-many database relationship in Postgres).<br>
31
+
5. Responds to GET, POST, PATCH, and DELETE (RESTful API) requests in order to allow for cart and orders to be properly deleted.<br>
32
+
6. Implements proper naming conventions for routes.<br>
33
+
7. The web app implements the ability to reset the database to its default state in order to create a clean slate and create a consistent UX.<br>
37
34
38
35
[gif goes here]
39
36
40
-
### Frontend
41
-
42
-
7. Sneaker World serves an appropriate 404 page when no matching route is defined
43
-
8. The application implements a like feature without navigating out of the page
44
-
9. The application uses dynamic frontend routes created with React Router.
45
-
10. Sneaker World uses hierarchically designed React components that includes:
46
-
homepage, products, details, cart, and checkout.
47
-
11. Sneaker World uses components and presenter components to streamline the application.
37
+
### Frontend Features
38
+
8. Sneaker World serves an appropriate 404 page when no matching route is defined.<br>
39
+
9. The application implements a like feature without navigating out of the page.<br>
40
+
10. The application uses dynamic frontend routes created with React Router.<br>
41
+
11. Sneaker World uses hierarchically designed React components that includes: homepage, products, details, cart, and checkout.<br>
42
+
12. Sneaker World uses components and presenter components to streamline the application.<br>
48
43
49
44
[gif goes here]
50
45
51
-
### Custom
46
+
### Custom Features
52
47
53
-
12. Sneaker World filters and/or sorts based on user preferences.
54
-
13. The application gracefully handles errors.
48
+
13. Sneaker World filters and/or sorts based on user preferences.<br>
49
+
14. The application gracefully handles errors.<br>
0 commit comments