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

Responsive Result Summary Page

Pratham•10
@PrathamS1
A solution to the Results summary component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Difficulties:

  • The major difficulty I faced is at the end, to make the solution responsive according to the android preview given. What I did was close to that preview but not the right one.
  • I have a very less understanding of the 'grid' property of CSS, and I knew that this solution could be made easily using that property. I didn't use the property.
Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Paweł Chudecki•860
    @SoulRvr29
    Posted about 2 years ago

    You can center everything in an better way. Remove margin-top: 10%; from container and add:

    body{
    min-height: 100vh;
    display: grid;
    place-content: center;
    }
    

    or if you want to use flexbox:

    body {
    min-height: 100vh;
    display: flex;
    flex-direction: column;
    align-items: center;
    justify-content: center;
    }
    

    This guide helped me a lot in understanding grid: click here

    Marked as helpful
  • Salah Shadoud•240
    @SalahShadoud
    Posted about 2 years ago

    Hey There! Congrats on Finishing the Challenge. i have a few notes for you and may this help you in your future challenges and projects:

    • You missed the summary resutls background colors, you can achive that by using the values they gave in the style-guide file in the hsla(Hue, Saturation, Lightness, Alpha) function, this way u can benefit from the alpha value that is responsible for the transperancy of the color.
    • Grid Property is a time saver property especially when it comes to ressponsive desings, so i recommend you to learn using it and start applaying it in your challenges, and here is a good video that will help u learn it in the easy way, Link Here
    • i recommend to follow the Mobile-first approach and it works by starting your work from small screens and gradually working up to larger screen sizes.

    hope this will be helpful, Happy Coding

    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

Oops! 😬

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

Log in with GitHub