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

result summary

Yung Josh•20
@yungjosh234
A solution to the Results summary component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


This project was my very first challenge as a beginner which took me about 4 hours but by God's grace I found it amusing and quite interesting and now i'm more curious to find out how the rest challenges will be like. Thank you.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • hitmorecode•7,560
    @hitmorecode
    Posted about 2 years ago

    Nice well done. Just a few tips

    • If you have an element with a class or id, when applying css you can target the class or id of that element directly. .section1 .result-title you can remove .section1 and just target .result-title directly. What you are doing is handy when you have elements without a class or id for example:
    <section class="section1">
        <p>something</p>
    </section>
    <section class="section2">
        <p>something</p>
    </section>
    

    If you want to target only the <p> inside .section1 then you can do it like this .section1 p {}

    • If you add min-height: 100vh; on the body and apply flexbox, you can remove the margin on the container. Flexbox will place the card in the middle of the page. This is much better for responsiveness of the page.

    • When structuring your html, try to make a good habit of doing like this

    <body>
      <main>
        /* everything goes in here */
      </main>
    </body>
    
    Marked as helpful
  • nirglus•270
    @nirglus
    Posted about 2 years ago

    Hey, congratulations on you first challenge! I have a few tips to achive closer results:

    Firstly, I recommend you to read about linear-gradient property. With the linear gradiate you can achive the same backgrounds of the left side and the score circle. You also have the proper colors at the style-guide file.

    Secondly, try to add transparency to the summary blocks by using rgba colors. For example: rgba(255, 87, 87, 0.06) the forth parameter sets the transparency. It goes from 0 to 1, try to play it to match the perfect color.

    Keep up the work and good luck!

    Marked as helpful

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

Oops! 😬

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

Log in with GitHub