Refactor Tractor

What is this?

This was a Mod 2 project for Turing's front end engineering program, exploring refactoring and interacting with a code base previous developers have built. This was our first time integrating webpack, fetch API, Sass, chair spies, and breaking our styling and JS functionality into various files. The goal was to take a code base intended to meet a previous project spec, and after matching the first spec follow outlines of this next iteration to refactor and build upon the functionality.

Who was involved?

Stacy Potten,
Nathaniel Millard,
Tim Keresey

How to use it?

The site is deployed Otherwise getting into the code itself

Clone Down This Repo
Run NPM Install
Run NPM Start to start your server
Open this link in your browse
Any edits are now live in real time

Technologies Used

Javascript
html
Sass
Webpack
Lighthouse
Fetch
Mocha
Chai
Chai Spies

How did it go?

Generally speaking this project was a challenge: both in scope, time, and content in context of our previous work. There was a lot of room for small errors in one place trickling down farther away as we implemented more modular functionality. This was also the most difficult/inconsistent data we have handled, which inspired a lot of thinking on our toes and staying flexible. And generally there just was a steep learning curve on such a wide range of new concepts happening at once. That being said. For a project implementing so many new concepts, we are proud of the work we were able to get done. We excelled at dividing work and learning, so that one developer didn't have to self-teach every concept, but rather individual memebers could prelearn, and then teach the team. Every developer had time to indivdually problem solve, as well as plent of room to trouble shot as a team. And the project we have now, is a vast improvment of what was unzipped.

Where can we go now?

While this project isn't open for contributions, or expected to be maintained, with more time and interest there are a few features to consider - Better utilizing tags, while they are searchable, they aren't currently displayed. - A more flexible user interface, allowing a log in to the user knows "who they are", or even the ability to make a new user - We also thought of having households, and users could be extended child classes of this parent class. This would allow users to inherit a pantry and pantry methods, while individuals could have different favorite recipes than one another and new unique values and methods given that.