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

Responsive result summary dashboard created using HTML, CSS, FLEXBOX.

bootstrap, react
Mayowa Oladimeji Oyinlola•30
@hillar10n
A solution to the Results summary component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


the challenge is much more easier than i thought, i was able to see through the designer's layout and the approach to it.

so i made use of flexbox and css3 in building this and it took me 3hrs to solve.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Ted Rinquest•440
    @climb512
    Posted about 2 years ago

    Hi, nice looking design!

    The issue with the button positioned at the far bottom of the Summary pane can be easily fixed with Flexbox. I saw you used Flex in many other places, so it will be easy for you:

    .result { display: flex; flex-direction: column; justify-content: space-around; /* or space-between */ }

    Then remove the margins and fiddle with padding on all the <div>s with the #ids, and the right-hand pane can be nice and compact like the example.

    Keep coding!

    Marked as helpful
  • Arber Lisaj•320
    @arberlisaj
    Posted about 2 years ago

    Hi @hillarionCodes I would like to congratulate you on completing the Results summary component and I might have a couple suggestions regarding your solution

    • A semantic element clearly describes its meaning to both the browser and the developer so instead of spamming a bunch of divs it would be a lot better to use semantic elements like for example <div class="container"> should be replaced with <section class="container"> or even <main class="container"> and instead of <div class="result"> you want to use <section class="result">
    • In the right container where the results are displayed you want to add some padding so the button doesn't touch the border it would be a lot more aesthetic from a designers eye

    All in all good solution and i wish you a long time in the community

    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

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