Game Archive Presentation

Transcript

1. Game Archive Adam Alam Avery Shepherd Chris Calizzi Haris Bhatti Rani Patel
2. Demo http://gamearchive.us
3. ER Diagram
4. Creating Models
5. Our API & Source API Source API: https://api-docs.igdb.com/#endpoints Main.py: https://gitlab.com/adam_alam/cs331e-idb/-/blob/master/main.py Documentation for Our API: https://documenter.getpostman.com/view/15091338/TzJx8wQ4
6. Frontend Structure Displaying and Interfacing Data
7. Unit Tests Adam: 5 Avery: 5 Christopher: 4 Haris: 3 Rani: 17
8. Issues Adam: 31 Avery: 10 Chris: 6 Haris: 5 Rani: 15 Unresolved Issues: 5 • Wanted to add more styling Resolved: 61
9. Our Own Critique • What did we do well? a. Have many instances and pictures for each pillar. b. Cool splash page with video and nice styling. c. Loading animation when data we are waiting for data to be served. • What did we learn? a. Databases b. Deployment c. React • What can we do better? a. Instance pages is a basic and could be styled better. b. Arrows/Animation for descending/ascending on the tables • What puzzles us? a. Optimizing image loading page on developer page. b. We tried automated deployment on each commit to master but we ran into obstacles
10. Group 13 Critique • What did they do well? a. Well organized about us page. b. Arrows change depending on descending or ascending order. • What did we learn from their website? a. How to use a nice image gallery for each pillar. b. Footer adds nice touch to a website. • What can they do better? a. Add many more instances. b. Style each of the instances pages. c. Add images on each instance. d. The background instance can be noisy on instance pages. • What puzzles us about their website? a. The nav bar changes text to show current page where something like the home page or a logo should be b. The connections for each instances aren’t clear as links.