See here

1. Contributors
2. Project Overview
3. How to use the app
4. Technologies Used

• 🥗 Nichele Dunn 🥗
• 🌮 Sydney Bear 🌮
• 🥗 Kat White 🥗
• 🍱 Erica Spitz 🍱

• Build on top of pre-existing code that you did not write and navigate someone else’s codebase
• Make network requests to API endpoints to retrieve and manipulate data
• Refactor pre-existing code and use inheritance to DRY up repetitive logic
• Ensure your app is following best practices for accessibility
• Leverage Sass to DRY up your CSS
• Incorporate Webpack to streamline your workflow process

This was our first experience being presented with someone else's code and nearly complete website. To be honest, we were frozen in place at first. Seeing all the different ways someone could address logical issues - ways that we had not tried ourselves or even ever considered ourselvs - was a real challenge. We only began to genunilty understand this codeblock after jumping in.

1. We began by setting up our APIs - so that we could ensure we had the correct data path as we began refactoring.
2. We then built out the class structure to be clearer and more robest.
3. We then starting putting out all the small fires - functionality that didn't work, unresponsive aspects, missing images, etc. These small fires often led to larger fires in the javascript logc.
4. With a working and functional website in place, we startd to untangle the javaScript that manipulatd the DOM from the logical functions.
5. With a cleaner and more scalable file structure - we started to address accessibilty issues - ensuring that our website passed WAVE and Lighthouse.
6. And finally! We implemented Sassy CSS.

To set up the data server, run the following commands:
git clone [email protected]:turingschool/What-s-cookin--starter-kit-API.git
cd What-s-cookin--starter-kit-API
npm install
npm start
Then, open a new Terminal window

In the new Terminal window, run the following commands:
git clone [email protected]:k-atwhite/whats-cookin.git
cd whats-cookin
npm install
npm start
Open a window in your web browser of choice, and visit localhost:8080 to view the app!

• HTML
• CSS
• JavaScript
• Webpack
• ESLint

1. Understand Webpack bundler
2. Include All Functionality from Original Spec
3. Fetch data from local server
4. Identify redundant code in your classes and opportunities for DRYing it up
5. Refactor within your classes to create dynamic methods that use arguments/parameters for changing their behavior
6. Refactor across your classes to create a parent class that others inherit methods from as appropriate OR be able to defend your choice for not using inheritance.
7. DOM manipulation should be organized into its own domUpdates.js file. And then will be called in the scripts.js
8. Refactor the existing CSS into Sass. Making use of:
   1. variables for colors, fonts, etc.
   2. nesting, when/where appropriate
   3. at least two mixins or extends
9. Accessibility
   1. Your app should be fully responsive from mobile devices - tablets - laptops
   2. You must be able to tab through your app and use it without a mouse
   3. Your app must still be usuable when tested with a colorblind extension
   4. You must score as close to 100% as possible with the “Lighthouse Accessibility Audit”. Be prepared to explain any accessibility audits your application is failing.
   5. Your HTML must be written semantically and ARIA tags should be used (ONLY if needed / appropriate)
10. Testing
    1. Initial values of class properties need tests
    2. Class methods need tests for all expected outcomes
    3. Any methods that modify class properties should be test
    4. You are not required to test your fetch calls