travel-tracker

Travel Tracker

Abstract

Looking to book a trip and get away? Use this repo to help you do just that! This was a solo project assigned by the Turing School of Software and Design designed to create a travel tracking application which utilized a variety of technologies. These technologies included javaScript, HTML, CSS, Mocha, and Chai. This project marks the half way point in our education related to this program, primarily focusing on vanilla JS to this point. The project was completed in one 4 day push. The project goals were to: user OOP to drive the design of the application and the code, work with an API to send and receive data, solidify the code review process, and create a robust test suite that tests all functionality of the client-side application while ensuring that our app follows best practices for accessability.

feel free to check out the deployed github pages link (https://crpearce.github.io/travel-tracker/)

User login

2022-09-27 08 13 48

Display view and data entry

2022-09-27 08 20 23

Book Trip Entry

2022-09-27 08 44 40

Update User View

2022-09-27 08 46 03

Setup

That’s right, clone not fork. You will use this repo multiple times, but you can only fork a repository once. So here is what you need to do to clone the repo and still be able to push changes to your repo:

  1. Clone down this repo. Since you don’t want to name your project “webpack-starter-kit”, you can use an optional argument when you run git clone (you replace the [...] with the terminal command arguments): git clone [remote-address] [what you want to name the repo]
  2. Remove the default remote: git remote rm origin (notice that git remote -v not gives you back nothing)
  3. Create a new repo on GitHub with the name of [what you want to name the repo] to be consistent with naming
  4. Copy the address that you would use to clone down this repo - something like git@github.com:...
  5. Add this remote to your cloned down repo: git remote add origin [address you copied in the previous step] - do not include the brackets

Now try to commit something (just add a line in the README) and push it up to your new repo. If everything is setup correctly, you should see the changes on GitHub.

Setup pt. 2

After one person has gone through the steps of cloning down this repo and editing the remote, everyone should clone down the repo.

Then install the library dependencies. Run:

npm install

To verify that it is setup correctly, run npm start in your terminal. Go to http://localhost:8080/ and you should see a page with the Turing logo image and a beautiful gradient background. If that’s the case, you’re good to go. Enter control + c in your terminal to stop the server at any time.

Login

  1. To login to the dashboard view for a user, please use the current username and password format.

username: traveler50 (where 50 is the ID of the user, users 1 - 50 should be acccessable)

password: travel

Testing

There is no boilerplate for testing in this starter-kit repo. You will need to set this up yourself. However, if you ran npm install, then the tooling you need to start testing is already installed (mocha and chai).

Project Specs

The project specs and rubric for Travel Tracker can be found here

Technologies Used

## Challenges

Wins

Future Extensions