mrpeski / fend-capstone

mrpeski/fend-capstone Issues

Allow the user to remove the trip.
Closed 2 years ago
Use Local Storage to save the data so that when they close, then revisit the page, their information is still there.
Closed 2 years ago
There should be at least one test for the express server and application javascript
Updated 2 years ago1
Webpack config should contain at least 3 scripts, express server, build and test. Additionally, dev server may be included.
Closed 2 years ago
The project should have a structure like the one shown
Closed 2 years ago
Integrate the REST Countries API to pull in data for the country being visited.
Updated 2 years ago
Pull in an image for the country from Pixabay API when the entered location brings up no results (good for obscure localities).
Updated 2 years ago
Add end date and display length of trip.
Updated 2 years ago
Code is formatted with consistent, logical, and easy-to-read formatting as described in the Udacity JavaScript Style Guide.
Updated 2 years ago
Comments are present and effectively explain longer code procedure when necessary.
Updated 2 years ago
A README file is included detailing the app and all dependencies. Other requirements: The Readme file should have non-default text in it that is specific to this project. It doesn’t have to be thorough, but should have some basic info. Bonus points if correct markdown is used.
Updated 2 years ago
At least one option from the Extend your Project/Ways to Stand Out sections have been added. Please add a Note to your reviewer which one you chose to implement, or add into your README.
Updated 2 years ago
There should be URLS and API Keys for at least 3 APIs, including Geonames, Weatherbit, and Pixabay. You can feel free to use more than 3 APIs. There should be a primary object with placeholder member value pairs. There should be a primary function that is exported to index.js.
Updated 2 years ago
At least one function should be imported. At least one event listener should be imported. (styles referenced in html/css)
Updated 2 years ago
Server should be a near duplication of project 3 with the exception of additional added member: value pairs.
Updated 2 years ago
The design should clearly be different from the design used in projects 3 and 4.
Updated 2 years ago
HTML structure should be indented properly with classes and ID’s that make sense.
Updated 2 years ago
Styling is set up in a logical way. All interactive elements have hover states.
Updated 2 years ago
All features are usable across modern desktop, tablet, and phone browsers.
Updated 2 years ago
The project must have service workers installed.
Updated 2 years ago