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

Results Summary Component using Flexbox

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

Solution retrospective


I struggled a lot to get the score into the circle as per the design. Not sure what I'm doing wrong

Any other feedback will also be greatly appreciated! This is my very first HTML and CSS "project" I've ever made and I'm eager to hear any feedback so I can (hopefully) do much better on my next one

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Victoria Azola Silva•1,290
    @VickyAzola
    Posted almost 2 years ago

    Hi, 👋 welcome to the community! 👩‍💻 👨‍💻 Nice work finishing this challenge.

    A few tips I can give you:

    • To center the card vertically and horizontally, you can use grid or flex on the body, like this:

    With grid

    body { 
        min-height: 100vh;
        display: grid;
        place-content: center;
        font-family: 'Hanken Grotesk', sans-serif
    }
    

    With flex

    body { 
        min-height: 100vh;
        display: flex;
        flex-direction: column;
        justify-content: center;
        align-items: center;
        font-family: 'Hanken Grotesk', sans-serif
    }
    
    • Fix the container, let only the display flex, and delete the set width and height. Also, the default direction of flex is always row, so you don't need to specify it (unless you want a diferent direction). The class parent would look like this:
    .parent {
        display: flex;
    }
    
    • To center the circle, you can use margin auto. And to center the content in the circle, use Flex, like this:
    .overall-score {
        margin-inline: auto;
    
        border-radius: 50%;
        background-image: linear-gradient(hsla(256, 72%, 46%, 1), hsla(241, 72%, 46%, 0));
        text-align: center;
        width: 200px;
        height: 200px;
    
    //to center the contetn
        display: flex;
        flex-direction: column;
        justify-content: center;
        align-content: center;
    }
    
    • Also, remove the defaul margin on the h1 and h5 and use a bigger font-size on the h1:
    .overall-score h1 {
        color: hsl(221, 100%, 96%);
        margin: 0;
        font-size: 80px;
    }
    
    .overall-score h5 {
        color: hsl(241, 100%, 89%);
        margin: 0;
    }
    
    • For the button, add border: none;
    • And on hover, add the color and pointer:
    button:hover {
        background: linear-gradient(hsl(252, 100%, 67%), hsl(241, 81%, 54%));
        cursor: pointer;
    }
    

    Hope this helps! 🤗

    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