Where2 is an aggregation based search engine for locating Restaurants and Events for an upcoming vacation. The original plan was to build an application that would allow clients to plan their trip in advance favoriting places they wanted to visit while out of town.
Steps for Using the Site:
- Select a Start Date (the application will default to Today)
- Select an End Date (the application will default to 7 Days from Today)
- Enter a Destination: City around the World (this is backed by Google Places API - and will only accept known Google Locations)
- Select a Search Radius (default is 10 Miles; Up to 100 Miles by 10 mile increments)
- Click Search... Please Note: Login features with Email does work but is not fully integrated with Favorite Feature
- Google Places - API \ Library - Used for Destination Resolution - Reduces chances of unresolved locations
- Firebase Auth and UI - Site supports User Authentication via Email Provider and utilizs the Firebase UI
- Firebase Database - Site is backed by Firebase for User Favorites Tracking
-
- When User is Authenticated - User Account created for Favorites in Realtime Database *
-
- Bootstrap - Primary CSS - Modal, Accordian, Carousel, Grid, Button, Form Control
- Moment JS - Used for the Eventbrite API to format Time properly for queries
- Yelp API - Used for Restaurant Results
- Zomato API - Used for Restaurant Results - Had plans to use thier other API's for Restaurant Results
- Eventbrite API - Used to collect Events for a location
-
Craig Wilkey GitHub Profile
- Project Planning (in the beginning): Once the idea was established; I helped to drive the list of work items we would need to get a framework started.
- Initial Website Tempalte with Firebase and Javascript: Utilized my Default Template for creating our Site.
- Created the initial DEV Experience - Form Boxes for a client to Submit and the Javascript Object for storing these values - This enabled each person to work off the same base for their API investigations.
- Zomato API: Initially responsible for working with the Zomato API to determine if our planned input would provide an appropriate output.
- Enabled Firebase Authentication for user login to site.
- Enabled Firebase Database to enable user Favorites.
- Scrapped Favorites solution due to time and current state of bugs.
- Javascript as an Object; tried to use an Object for everything but it slowly got out of control
- Overhauled the Card Print feature that was per API to be a single Function for all Cards to be Printed with.
- Worked with Suzanne on implementing a fix for Zomato API where image URLs were blank
- Worked closely with Zach on issues as we were stuck with API or UI design problems.
- Lot's of Bug Fixes
-
Zachary Holland GitHub Profile
- Project Management during 2nd half; delegated tasks to other group members as we got to D-Day
- Wrote the API ajax calls for querying Yelp and Eventbrite.
- Developed the card accoridion content container
- Created the initial card generator for the API data
- Primary front end and UI design:
- Design implementations were taken from other sites such as Eventbrite and Yelp.
- Developed the smooth scrolling for the website when clicking the submit button
- Implemented UI features to simplify user experience;
- Put a to top button in the footer but only when at certain part of page
- Created an inner scroll inside the card content accordion to contain the results to a managable view
- Designed the image carousel with full scale background images