https://i.imgur.com/E4wkq3e.png
At first it was a pretty daunting to try and think of how we were going to divide this project up and trying to fit it into all one tag seemed, it seemed a little too complicated. So we decided to split up the badge-list, the badge itself and potentially the search box all into a webcomponent to keep things clean and neat as well as to help with the understanding the overall scope of the project. We had trouble trying to figure out what to attack first so we just started with creating the badge and ripping the css from the website itself and iterating until we have something that we feel looks similar enough to the example website. CSS Styling has been a little frustrating as well as using the 'display' property in order to achieve a look as similar as possible to the example website. From project one we brought over the ideas of creating custom web components to make the project more reusable, understandable, and just better looking overall. General knowledge of the interactivity of CSS, HTML and JS in order to produce a working website. Once we get the badge done, out priority is to get the search APIs done and this is due to a multitude of reasons. Mainly we want to be able to iterate and debug search early on and get that out of the way as quick as possible. This is structured this way because we want to style when have search finished so that we can account for how the website is supposed to look when a search request is fulfilled (I.e there is only one badge on the page as opposed to five). For some reason our border-left property isn't working, it doesn't even show in the debugger in chrome but all other properties do (including border).
Top comments (0)