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

Results Summary Component

Myro Joy Lee•120
@myrojoylee
A solution to the Results summary component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


I had problems recreating those partial borders around the Memory/Verbal/Visual/Reaction. I'd never done before, only full borders, so I skipped that part in my CSS. All the solutions I found on Stack Overflow or elsewhere were pretty intermediate/advanced for me and I just couldn't understand them lol. But here is my attempt at the rest of it minus the partial borders...found a codepen to center the entire thing upon window resize and credit is given within. Feedback welcome :).

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Bilal Türkmen•340
    @bilalturkmen
    Posted over 2 years ago

    Hi, nice work. i think it can be improved a bit 😊

    no need to use js to center an element.

    ✅css grid or flexbox is enough for this. to center an element over the viewport area you should add min-height property to body selector like this

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

    and then you can delete the index.js. you dont need that anymore. you can also delete this div

    • your media query breakpoint stays small for the width of the card design. should be expanded a little more like this
    @media screen and (min-width: 768px) {
    }
    
    • and this div

    ✅ can be replaced as main because document should have one main landmark.

    • same this div

    ✅ can be replaced as h1 because page should contain a level-one heading

    i hope these helpful 🙂

    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 1st-party linked stylesheets, and styles within <style> tags.

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.

Oops! 😬

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

Log in with GitHub