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

Stats preview card component first attempt

Hannah O•80
@hannahro15
A solution to the Stats preview card component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Hi, any feedback would be helpful. The only thing I had issue with I think is the background colour of the image and lining it up in the top and right sides of the container. Other than I don't think it is too bad. I don't know why when I click preview code it looks different from the screenshot. The screenshot also looks very different from when I looked at my design in the browser. Thanks.

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • Tabassum Fatima•215
    @tab21
    Posted over 3 years ago

    @hannahro15 hi !

    Congratulations on completing this challenge. However, I have some suggestions for the same.

    first about your question it may be that you designed your project specific to a width which wasn't 1440px as the ss here it takes the image of how your project looks at this width which is a desktop width generally.

    HTML: I suggest you make a div around all the written part (like .text)so that its easier to place as all are aligned to each other.

    CSS : Here don't repeatedly use the same things and write your code again as you have done for box-1,2,3 and number-1,2,3 and text-1,2,3. as they all have the same style just give them the same class and write the code once only. and in number and text you don't even need to give classes as they have different tags eg:

        margin-bottom: 5px;
        font-family: "Inter";
        color: hsl(0, 0%, 100%);
    }
    
    h4 {
        font-size: 8px;
        font-family: "Inter";
        color: hsla(0, 0%, 100%, 0.6);
    }
    /* since they have the same font family you can just give this font family to all */
    

    don't give padding to div since it gives space between img and container instead give padding to text you have wrapped around all the written parts. And also don't give flex-container 100px rather 100% width so that it can place the contents in it all over the .text

    .text {
        padding: 5%;
        width: 45%;
    }
    
    .flex-container {
        width: 100%;
        display: flex;
        justify-content: space-between;
        align-items: center;
        text-align: center;
    }
    

    for making it responsive I suggest using flex and making the width and height of the container auto and making the width of the picture 100%

    @media screen and (max-width:800px) {
        .container {
            display: flex;
            flex-direction: column;
        }
        main {
            width: auto;
            height: auto;
            overflow: hidden;
        }
        img {
            width: 100%;
        }
        .text {
            width: 90%;
        }
    }
    

    for the purple part in the image, you can give the colour to imgdiv and lower the opacity of the img

    .imgdiv {
        background-color: hsl(277, 61%, 48%);
    }
    
    img {
        opacity: .5;
    }
    

    also, add border-radius to the container

    I hope this helps :)

    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