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

Responsive result summary component

Ameya kawade•30
@Cool-developer-975
A solution to the Results summary component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Any suggestions?

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

  • Nuria Torres•110
    @nuria1110
    Posted almost 2 years ago

    Hi! Looks like a great start, just a few suggestions:

    • If you want to use a mobile-first approach, meaning you start writing your CSS for smaller screens first, your selectors do not need to be within a media query. You can write your base formatting as you did with the body selector and then as you increase your screen size, change your property values, same goes as for the rest of your selectors, e.g.:
    body {
      font-size: 12px; 
    }
    
    @media (min-width: 750px) {
     body {
      font-size: 14px; 
     }
    }
    
    @media (min-width: 1440px) {
     body {
      font-size: 16px; 
     }
    }
    

    This can also be the other way around, you can write your initial formatting for bigger screens and then as your screen size gets smaller use media queries to change your values.

    • If there are values you know you will be using more than once, you can create variables in your root CSS to avoid having to repeat yourself or make it easier to use them. I mostly use this if I have a number of specific colours I know I'm going to need:
    ::root {
      --light-lavender-color: hsl(242, 15%, 65%);
    }
    
    .container {
      background-color: var(--light-lavender-color);
    }
    
    • If your border radius around your card is the same, e.g. 30px, you can just use border-radius: 30px; instead of repeating yourself:
      border-top-left-radius: 30px;
      border-top-right-radius: 30px;
      border-bottom-left-radius: 30px;
      border-bottom-right-radius: 30px;
    

    I hope this helps! I have also completed this challenge so feel free to have a look :)

    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
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