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

Result Component Summary

Aviad Churaman•210
@av1ad
A solution to the Results summary component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


I found doing anything in css difficult, I spent 3 hours just on the mobile design which I found out was very flawed along with my code for desktop version. I tried doing variables for the colors but when it came down to the light red, cobalt blue, etc. colors I kind of choked due to the alpha, I found out that I was adding too many parathenses while typing out hsla. My question for best practices is just how do I make cleaner code? I feel like Everything is everywhere, my html feels like its missing tags, I'm not sure if I was supposed to put classes for every single element, my css was everywhere as well felt like I was writing things just to write them and see if they worked.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Mohammed Fakih•1,590
    @javascriptor1
    Posted about 2 years ago

    Hi Aviad ,

    Here are some notes about your solution :

    • You should use IMG tag for icons instead of <embed>, which will not display the icons on the page.

    • You should import bolder versions of the design font so you can use them.

    • From the summary section, remove the background and box shadow.

    For the use of classes, No - you are not supposed to use classes for each project but it's always better to use them. Classes have several advantages like Reusability where you can use the same code for more than one element/case which helps modularize your code.

    Keep coding!.

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.

Oops! 😬

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

Log in with GitHub