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

Stats Preview, using CSS Flexbox

matthewohreluy•105
@matthewohreluy
A solution to the Stats preview card component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


I would appreciate any feedback.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Ahmed Faisal•5,095
    @afrussel
    Posted almost 4 years ago

    Good work. Nice try. Use the below code for image section.

    .img-mono {
        -webkit-filter: grayscale(100%);
        filter: grayscale(100);
        opacity: 0.8;
        mix-blend-mode: multiply;
    }
    
    Marked as helpful
  • darryncodes•6,350
    @darryncodes
    Posted almost 4 years ago

    Hi Matthew,

    Great solution!

    It might be worth resolving your accessibility report as a good practice change <div class="container"> to <main class="container"> and <div class="attribution"> to <footer class="attribution">. Also have at least one <h1> in your design.

    All the best!

    Marked as helpful
  • Raymart Pamplona•16,040
    @pikapikamart
    Posted almost 4 years ago

    Hey, great work on this one. You already have some feedbacks from others, but i'm just going to add some.

    • On your body tag, avoid using a fixed height: value vh property, on your case height: 98vh will limit your element's height based on the remaining viewport's height. If you inspect your layout in dev tools at the bottom, hover on the body tag, you will notice that it doesn't really captures the whole content like it should do. Instead, replace that with min-height: 100vh, this will expand the container if it needs to.
    • Remove the width: 100vw on the body tag, this creates a horizontal scrollbar.
    • The information about the company should have been wrapped inside a ul and li element, since those are list of information.
    • The text as well for the company information, using heading tags on those is not really great because it doesn't really add any more information. Better to just use a p tag on them, I am talking about the 10k+ elements.

    Aside from those, great work.

    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

Oops! 😬

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

Log in with GitHub