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

Stats preview card component solution

Ashwani Pandey•180
@ashwanipydev
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 wanted to start my frontend journey, but I am facing a lot of problems in my code. Please help me out with this situation; I feel so tired. I have some questions during this project. Please review and give me some answers on how to remove the errors in the project. Q1: How to deal with images to make them responsive on any screen width? Q2: How to add a gradient to an image? Constructive criticism is also welcome.🤔

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • hitmorecode•7,540
    @hitmorecode
    Posted about 2 years ago

    Congratulations well done. I took a quick look at your markup and css and from what I've seen, it's not that bad. I've seen worst than this. You are in the right track.

    /* Q1 as for the images you can use the picture element, you'll have to do some adjustments to fit you page, but this works */
    <div class="right_card card">
    <picture>
    <source media="(min-width: 900px)" srcset="images/image-header-desktop.jpg">
    <source media="(min-width: 700px)" srcset="images/image-header-mobile.jpg">
    <img src="images/image-header-desktop.jpg" alt="">
    </picture>
    </div>
    
    /* Q2 this is how you can solve ti*/
    /* add a background color to right card, you are going to use this to blend with the image */
    .right_card {
    background-color: var(--soft-violet-accent);
      
    }
      
    .right_card img{
    display: block;
    width: 100%;
    height: 100%;
    object-fit: cover;
    border-radius: 0 10px 10px 0 ;
    mix-blend-mode: multiply; /* to blend the background color of the card with the image, you can use mix-blend-mode and set it to multiply */
    opacity: 0.8; /* add opacity to it, and play with the opacity until you get what you want */
    }
    
    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