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

Stat preview card component with flexbox

Mohammad Ebrahimi•250
@moheb2000
A solution to the Stats preview card component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


1- I used object-fit: cover for image> Is there any better approach? 2- To colorizing image I used a violet box with low opacity. Is there a better way for this problem?

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Abdellah el aajjouri•190
    @abdellahelaajjouri
    Posted over 3 years ago

    Your card looks good , just decrease the height using max height and aligne it the content , Keep up 👌

    Marked as helpful
  • Abdo Achhoubi•330
    @abdoachhoubi
    Posted over 3 years ago

    The card is perfect 👌 but consider placing it in the center, try changing the height of the body to "100vh", and then change it's display to flex, and make the justify-content: center / and align-items: center. Take a look at my solution to learn more. https://www.frontendmentor.io/solutions/responsive-stats-preview-card-made-using-html5-and-css3--zCH01OJG

    Marked as helpful
  • PhoenixDev22•16,830
    @PhoenixDev22
    Posted over 3 years ago

    Hello @moheb2000,

    I have some suggestions regarding your solution :

    • To improve the image overlay effect you should look up blend modes. You don't need an extra div you can have the one div class="column cover", background color Use mix-blend mode and opacity to make it more like the design.

    • To center the card on the middle of the page , you can use the flexbox properties and min-height: 100vh for the <body>like this:

    body{
    display:flex;
    align-items: center;
    justify-content: center;
    width: 100%; 
    min-height: 100vh;
    
    
    • Forclass="stats" , it would be better if you use an unordered list <ul> with 3 items for the stats

    • The number and word have to be read together to make sense so need to be in the same meaningful element. so only a span or maybe strong tag needs to wrap the numbers. the words like companies should not be in paragraph tags. They don't need to be wrapped in anything as they are already inside a meaningful element (list item)

    Overall , your solution is good, Hopefully this feedback 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

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