between pages • Utilized bootstrap to dynamically shrink bar with smaller screen size • Implemented animated links to create subtle call to action buttons.
sliders ◦ Included many filterable and sortable attributes to allow for concentrated searches • Imported a react slider to allow users to full and easy control of ranges
Maps - Genres -> Playlists -> Artists -> Events - Data is pulled once from APIs (stored in JSON files) then only from database Sorting - QueryBuilder - Modifications for sorting with -1 values Routing - Three get requests per model, many instances, some instances, one instance
Create multiple instances per model • Categorization of artists (improvement from phase 2) What did we learn? • Continuous integration is important • Connecting frontend with backend is cumbersome • Deployment takes time What can we do better? • Continuous integration • We could make our UI more eye-catching • Make data fetching dynamic • Add highlighting when searching What puzzles us? • How websites are able to pull quickly from APIs?
models • Designed a simple navigation system What did we learn from their website? • Most popular destinations are located on the coast of countries in the northern hemisphere What can they do better? • Display current value for range filters What puzzles us about their website? • Nothing! It is a good website 🙂
yeseniaperezcruz
geshan
vanstee
katarinadahlin
aleyda
techseoconnect
jonrohan
madoxten
mongodb
tamaranovitovic
nikkihalliwell
nmsamuel
