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

Stats preview card component

bociKond•150
@bociKond
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 found it hard to put color over an image and I am unsure about the responsiveness of the card.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Andrés Gutiérrez Ramírez•2,470
    @AGutierrezR
    Posted over 2 years ago

    Hello bociKond! Congratulation on completing this challenge! If I may, I could give you some solutions to the issues (accessibility and HTML)

    • Replace <section class="card"> for a <main class="card"> tag this will get rip of the accesibiltiy issues
    • Replace <article class="card__text"> for a <section class="card__text">, new the h1 issue will be fix.
    • You could replace the <div class="stats"> for a <ul class="stats"> and each <article class="stat"> tag in it replaces them for a <li class="stat">, you may need to remove the default style of a list but you will get a more semantic HTML.

    In regards to the image color blending, I use these CSS rules (adapted to your markup)

    .img {
      background-color: var(--clr-softviolet); /* hsl(277, 64%, 61%) */
      background-blend-mode: multiply;
      background-size: cover;
      background-repeat: no-repeat;
    }
    
    .img img {
      display: block;
      mix-blend-mode: multiply;
      opacity: 0.8;
      width: 100%;
      height: 100%;
      object-fit: cover;
    }
    

    Other than that, you may need to try various font sizes regarding the title and the stats.

    Marked as helpful
  • Hassia Issah•50,390
    @Hassiai
    Posted over 2 years ago

    Replace <section class="card"> with the main tag to fix the accessibility issue.

    For the color of the image, give .img a background-color of soft-violet, add mix-blend-mode: multiply; and opacity of 0.8 to the img.

    .img{
    background-color: hsl()
    }
    img{
    width:100%;
    height:100%
    mix-blend-mode: multiply;
    opacity: 0.8;
    }
    

    Hope am helpful.

    Well done for completing this challenge. HAPPY CODING

    Marked as helpful
  • Divine Obeten•2,415
    @Deevyn9
    Posted over 2 years ago

    Hi Bocikond, congrats on completing this solution, your solution looks really great, about the responsiveness, you did pretty good, However, you'll want to make the container take a column flex direction from 850px because that is the width where the image begins to shrink.

    I hope you find this helpful.

    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
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