I initially explored several different recipe APIs to find the functionality I wanted. After selecting one, I ended up having to make a change halfway through the project due to a lack of one category of information I needed.

The Dinner Wheel was easy to build with Winwheel.js, but manipulating the funcionality proved to be difficult. I was able to modify the dependency package to get the results I wanted after many hours of scouring Stack Overflow.

With only two weeks to get a working product, I was amazed at what I could build in such a short amount of time. Despite all the moving parts and discovering what I could and could not complete in the given timeframe, I am so proud to have integrated all the moving parts well and deliver an application so full of good functionality.

Despite my ability to customize the functionality of Winwheel.js, I also had trouble maintaining it after deploying the application. However, this opened me to the experience of modifying the dependency, saving it to my GitHub and using my own dependency in the project - something I would not have had to experiment with otherwise.

As I moved the information retrieved from the API down through the components, it became increasingly challenging to filter out irrelevant information.

Using CSS Grid also proved to be difficult in terms of responsiveness. However, I was able to learn much more about how Grid really works.

This project really helped me cement my understanding of JavaScript higher-order functions, as I often needed to use .map(), .filter(), and .any() in order to separate and compile retrieved information to display in the appropriate component.

I was able to set the application up to easily add game and route information for any of the other games in the main series by adding an array of route information. As I am able, I will be adding this information in without adjusting the app's functionality.