Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 3 months ago

Responsive Results Component

animation, accessibility
DangoDono•110
@CodingDango
A solution to the Results summary component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


What are you most proud of, and what would you do differently next time?

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.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community 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

Stay up to datewith new challenges, featured solutions, selected articles, and our latest news

Frontend Mentor

  • Unlock Pro
  • Contact us
  • FAQs
  • Become a partner

Explore

  • Learning paths
  • Challenges
  • Solutions
  • Articles

Community

  • Discord
  • Guidelines

For companies

  • Hire developers
  • Train developers
© Frontend Mentor 2019 - 2025
  • Terms
  • Cookie Policy
  • Privacy Policy
  • License

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

How does the accessibility report work?

When a solution is submitted, we use axe-core to run an automated audit of your code.

This picks out common accessibility issues like not using semantic HTML and not having proper heading hierarchies, among others.

This automated audit is fairly surface level, so we encourage to you review the project and code in more detail with accessibility best practices in mind.

How does the CSS report work?

When a solution is submitted, we use stylelint to run an automated check on the CSS code.

We've added some of our own linting rules based on recommended best practices. These rules are prefixed with frontend-mentor/ which you'll see at the top of each issue in the report.

The report will audit all CSS, SCSS and Less files in your repository.

How does the HTML validation report work?

When a solution is submitted, we use html-validate to run an automated check on the HTML code.

The report picks out common HTML issues such as not using headings within section elements and incorrect nesting of elements, among others.

Note that the report can pick up “invalid” attributes, which some frameworks automatically add to the HTML. These attributes are crucial for how the frameworks function, although they’re technically not valid HTML. As such, some projects can show up with many HTML validation errors, which are benign and are a necessary part of the framework.

How does the JavaScript validation report work?

When a solution is submitted, we use eslint to run an automated check on the JavaScript code.

The report picks out common JavaScript issues such as not using semicolons and using var instead of let or const, among others.

The report will audit all JS and JSX files in your repository. We currently do not support Typescript or other frontend frameworks.