FitLit

Abstract:

This application helps users see their fitness data, goals, and milestones in a user-friendly activity dashboard. The user data is sourced remotely and accessed through an API. It also allows an admin to view any individual's data, as well as a few key "bottom 10" data sets.

App Installation Instructions:

1. To get this app running, navigate to https://github.com/ericahagle/fitlit and clone it down from GitHub under the "<> Code" dropdown.
2. Open it from your terminal or preferred CLI with git clone <HTTPS or SSH key>.
3. Move (cd) into the directory.
4. Open the file in your code editor of choice, and you'll have everything you need!
5. The app can be viewed and interacted with in your browser of choice by using open index.html in your terminal.

Server Installation Instructions:

1. Navigate to https://github.com/turingschool-examples/fitlit-api
2. Clone the repo down to your preferred location (NOT within the main app repo)
3. Move (cd) into the directory on a separate terminal window from where you're running the front end
4. Run the npm install command to install the dependencies
5. Run the npm start command in your terminal to start the local server
6. Use ctrl + c to stop the local server from running in your terminal at any time

Preview of App:

Context:

This project was assigned during Week 1 of Module 2 in Turing's Front-End Engineering track. Part 1 of 2 had a timeline of 11 days from kickoff to due date. Part 2 was assigned during Week 4 of Module 2, and had a timeline of 5 days from kickoff to due date.

Contributors:

This application was built by Brendan Turner, Erica Hagle, Chris Butler, and Arden Ranta.

Learning Goals:

The goals of this project were to:

• utilize object and array prototype methods to manipulate data
• create a clear and user-friendly interface
• implement a robust testing suite via TDD
• make network requests to retrieve data
• prioritize DRY, reusable code
• practice professional and productive team collaboration

These were enacted on a MacBook Pro using GitHub, VS Code, Webpack, Google Chrome, the Mac Terminal, and Slack.

Wins + Challenges:

Wins:

• Consistent communication and respect for our DTR agreement
• Successfully refactored code to overcome challenges and match project rubric
• Utilizing individual strengths to divide workflow

Challenges:

• Figuring out how to efficiently connect all the separate local files and APIs while working asynchronously
• Getting comfortable and confident as a team in our GitHub workflow