- The API is being used by taking the properties in the roster.json file and sending it to the map in the team-roster.js file. That map is then rendered out in the .js file.
Since athletes are the basis of the card, the properties will consist of the name, position, stats/details label, as well as the more generic properties like an image and the top/bottom text. All this information from the backend is necessary in order to properly create "templates" for the athlete cards.
For Project 2, we'll have to use these same concepts to create micro frontends (badges) that can be easily replicated and altered individually. Once again, data will need to be pulled from a .json file by an API, then rendered with a map.
An example of the type of map that is going to be implemented:
Top comments (0)