On Day After Tomorrow a person can enter any city and a date in the near future to get the forecast for that day, a map of the city and a list of some cool things to do while there. It saves all searches and allows you to re-initiate those searches with the click of a button.
Github Link: https://github.com/david-leverenz/day-after-tomorrow Live Link: https://david-leverenz.github.io/day-after-tomorrow/
AS A USER that is planning to travel
I WANT to know the weather and points of interest according to that place and day
SO THAT I can plan more effectively and efficiently
GIVEN
WHEN I open the webpage
THEN is a search bar to input text, a place to input a desired date, and a search button.
WHEN a city is searched for
THEN I am presented with a map of the city, and relevant data around that location.
WHEN a city and date is searched for
THEN I am presented with a relevant weather forecast.
WHEN viewing the forecast
THEN the city name, temperature, and other weather related data is presented in a current and future forecast.
WHEN I am viewing the map
THEN I can interact with the map (click and drag, zoom, etc.)
WHEN I am viewing the location POI results
THEN the infomation contains the name, type of company, address, and phone/URL if applicable.
WHEN I search for a new city
THEN previously searched cities will be saved to local storage
WHEN I want to look at my previous searched cities
THEN I can see them on the page as buttons
WHEN I click on a given button
THEN it will take me to the result page with the respective location and date previously searched
WHEN I reload the page
THEN the previous search history data persists
- Two API CDNs must be used, one must be an original source.
- It must be deployed to GitHub with a working live link and contain a screenshot of the deployed site.
- The CSS CDN must be an approved CLI that is NOT Bootstrap.
- It must use multiple API calls that retrieve relevant data and display appropriately on the page.
- It must be user interactive and save/load user data with local storage.
- Quality README, comments, and organized clean code.
- Descriptive commit history and multiple branches.
=======
Our website uses the Tailwind CSS framework (a framework other than Bootstrap).
It was deployed to GitHub Pages.
It is interactive (i.e. can accept and respond to user input).
It uses two different server-side APIs (four api calls).
It uses modals for validation.
It uses client-side storage to store persistent data.
It is responsive.
It has a polished and easy-to-use UI.
It has a clean repository that meets quality coding standards (file structure, naming conventions, follows best practices for class/id naming conventions, indentation, quality comments, etc.).
It has a quality README (with unique name, description, technologies used, screenshot (to be added after CSS changes), and link to deployed application).
KT Eddy
GitHub Profile: https://github.com/kumih0
Ilia Glazman
GitHub Profile: https://github.com/ilia-glazman690
Karthik Murugappan
GitHub Profile: https://github.com/karthikmurugappan
David Leverenz
GitHub Profile: https://github.com/david-leverenz
Version 1.0 (Initial Release)
This project is licensed under the MIT License - see the LICENSE.md file for details.
Special thanks to Poornima, who got us over the finish line and our TAs, Dom and Sam,
who helped us through some frustrating roadblocks.
- Tailwind
- [Flowbite] (https://flowbite.com/)
- OpenWeather
- tomtom