Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted about 2 years ago

Responsive Results Summary Component

MIRZA ZEESHAN BAIG•40
@Mirza-Zeeshan
A solution to the Results summary component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Please provide your valuable feedback on my project. Specifically, I would like to know the following:

  1. How is the overall look and feel of the project?
  2. Is the content clear and easy to understand?
  3. Are there any suggestions you have for improving the card design or user experience?
  4. Are there any areas of the project where you experienced difficulty or confusion?

Thank you! for your valuable feedback.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Victória Nogueira Marques•390
    @victoriamnx
    Posted about 2 years ago

    - What does the overall design look like? It's perfect, I really liked it because I can see other projects that you've also done.

    - Is the content clear and easy to understand? Yes, perfectly understandable and clear.

    - Do you have any suggestions to improve card design or user experience? You can in the future make a box in the index that is in the style of the projects you've already done, but at the moment it's already very cool

    - Are there any areas of the project where you felt difficulty or confusion? No, I managed to understand very well and I really liked the result.

  • Durban86•320
    @Durban86
    Posted about 2 years ago
    1. The look of the project is very nice
    2. Content clear and easily understood
    3. I think you nailed it, for what the project is, not much to improve on.
    4. Some issues I had were the spacing on the summary icons and titles spacing between the scores.

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
Frontend Mentor logo

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.

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