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

Results Summary Component Solution

bootstrap
Mygaverse•150
@Mygaverse
A solution to the Results summary component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


I thought it was an easy challenge, but it took me quite a while to achieve the final result. There were some small issues with the layout and styles. I had to make several different approaches to the result. I did some reseaches and examples over the internet. I finally found a similar design that I could reference to. There are many techniques and skills that I can apply to my future projects. ps: I found there is a line of border around the left column. I haven't figure out where it went wrong. Let me know if you know how to fix it. Thanks!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • impiia•400
    @impiia
    Posted almost 2 years ago

    Hello! You've done a great job! Regarding the white line of border around the left column, you are using Bootstrap, which already has some styles. You are using the card class <div class="card">, and Bootstrap has a class called .card which already applies some styles, including the border around the left column (--bs-card-border-width: var(--bs-border-width);). In your code, you are overriding the .card class, but the styles applied by Bootstrap remain. To resolve this, change the name of your class to something else (for example, "my-card" in both the HTML and CSS), and the white line around the left column will disappear.

  • Thomas Hertog•885
    @thomashertog
    Posted almost 2 years ago

    The visual is looking good. There are some improvements available on the code part though

    HTML

    • the headings are not hidden
    • headings and their levels should be in order and still make sense (imagine stripping out all the other content, does it look like a sensible table of contents?)
    • there should only be 1 <h1>
    • you have a <div class="score-list"> with <div class="list-item">, which is completely insemantic. Use a <ul> with <li> for this
    • the <button> does not have a type attribute

    CSS

    • you've included bootstrap, but i don't really see it being used (and it's making things harder to adjust)
    • it's not responsive (not down to 375px at least, like in the challenge requirements)
    • i've got a feeling that a lot of styling is already in the HTML which made it more complex than it should be, keeping your CSS smaller (which i don't necessarily think is a good thing either)

    P.S. the border around the left column is coming from the border property in your .card selector (probably coming from bootstrap)

  • Redon•240
    @redoncapuni17
    Posted almost 2 years ago

    Well done for finishing the challenge

    As a front-end developer, your job is to make the website look just like the designer wants it to. If there are any differences, try to fix them quickly so that the website matches the design as soon as possible.

    This challenge consists of two parts: the mobile component and the desktop component. However, it appears that the mobile part has not been developed. It's important to address this issue and ensure that both the mobile and desktop aspects of the challenge are completed.

    1. Lack of semantic HTML:

    • Semantic HTML elements are missing or not used appropriately.
    • The structure does not convey the meaning and purpose of different parts of the webpage.

    2. Usage of absolute units instead of relative units:

    • Absolute units like pixels (px) are used for defining lengths and sizes instead of relative units like percentages (%), em, or rem.
    • Relative units are more flexible and responsive across different screen sizes.

    I hope you find this helpful and happy coding

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

Oops! 😬

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

Log in with GitHub