Responsive Results Component

Solution retrospective
I'm surprised how I got it so close to the target, Another thing is that I also added my own subtle animations to keep the page less static and more interactive. As for what I would do differently when tackling another challenge, I'd like to focus on developing the mobile version first. This is because dealing with a smaller screen size is more straightforward and simple. Whereas with a desktop screen size, there are many more nuances and complexities you have to keep in mind when it comes to laying them out.
What challenges did you encounter, and how did you overcome them?I encountered many challenges. For instance, Parsing JSON with fetch, Transitioning a background color to a linear gradient, laying out the elements in a consistent manner, and finding the right looking values for colors, font-weights, and font-sizes; Keep in mind that I did not use the given style-guide.
I was able to overcome these hurdles with persistence, yes, I struggled through this challenge. Firstly, I was able to learn how to parse a JSON through a 6 minute YT video. Secondly, I googled how to transition a regular background-color to a linear gradient, through transitioning opacity. And finally, I was able to get the values to look decently correct through tinkering.
What specific areas of your project would you like help with?I genuinely need some feedback on my semantics. Since I always start these challenges with an HTML first approach, I'd like my HTML to be as semantic as possible, reduce the usage of generic tags that hold no meaning like span or div when there's a more suited element for the context.
Please log in to post a comment
Log in with GitHubCommunity feedback
No feedback yet. Be the first to give feedback on DangoDono's solution.
Join our Discord community
Join thousands of Frontend Mentor community members taking the challenges, sharing resources, helping each other, and chatting about all things front-end!
Join our Discord