DEV Community

Platinumfish
Platinumfish

Posted on

Final blog post for wrapping up badge query project

My code's github repo- https://github.com/platinumfishes/badge-list

1- How many elements did you end up going with? Why did you break it up that way?

My partner and I went with four final elements that intersected with each other in the index.html. We decided on four elements because they each played an integral enough role within the project to warrant an entire element dedicated to itself. Our four elements were (1) Badge element, (2) Badge list, (3) Search Bar, (4) Page overlay.

The badge elements were the things being queried, and was our first element that we made. The badge list functioned as the thing that displayed what our queried elements were going to be with backend parameters, it also helped display all the badges upon initial page rendering. The search bar is the key query input that works with a .json file and badge list to get the user input to display the appropriate badges. The page overlay was purely visual, and helped organize our three elements into a more aesthetically digestible format.

2- What was the hardest aspect of this?

I would say the hardest aspect of this was the javascript logic connecting the backend to frontend, and just even knowing where to begin with it. Upon seeing our professor's example video, there were a lot of functions and methods that I would have never considered or didn't know about which were necessary to make the project work.

3- What part of this project was easier than you expected?

The easiest and most fun part was making the element parameters themselves, especially the CSS of each element and watching them fit together and produce the final result that you had been trying to get all along tickled a part of my brain that normal programming doesn't get to.

Top comments (0)