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

Stats Preview Card Component

Bryan Li•3,530
@Zy8712
A solution to the Stats preview card component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Couldn't get color to match for the image. Tons of time wasted cuz someone gave me terrible advice on a previous post to use <picture> for responsive images, but I couldn't modify it using css. So I just used another method.

Had major issues with the sizing of the divs for the mobile format. I would set the image-div to 40% height and info-div to 60% height. But neither one would adjust accordingly despite trying to set the parent div to have a set height.

Hope someone can help me figure this out. Thanks.

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • Jeje•2,050
    @AkoToSiJeromeEh
    Posted almost 2 years ago

    👋 Hi! Great work out there! In my experience creating this challenge, I used mix-blend-mode on the image to match the color in the design reference. Additionally, I noticed that you used display: flex on the <div> stats-div elements. I suggest using display: grid with a three-column setup (grid-template-columns: 1fr 1fr 1fr) to also match in the design reference also when it hit 375px of width i see the image is have a little gap you can use (vertical-align: middle;) on .main-graphic . That's all! I hope this helps and works for you. Thank you, and happy coding ! 🚀

    .image-div {

    position: relative;

    background-color: var(--theme-soft-violet);

    }

    .main-graphic {

    width: 100%;

    height: 100%;

    mix-blend-mode: multiply;

    content: url(./images/image-header-desktop.jpg);

    /* background-color: var(--theme-soft-violet); */

    opacity: 0.8;

    vertical-align: middle;

    }

    .stats-div {

    display: grid;

    grid-template-columns: repeat(3,1fr);

    margin-top: 50px;

    }

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 1st-party linked stylesheets, and styles within <style> tags.

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.

Oops! 😬

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

Log in with GitHub