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

Responsive Stats Card using HTML, CSS, and SASS

Adeel•55
@asab07
A solution to the Stats preview card component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Hello Everyone,

Here is my attempt at the responsive stats card exercise. I am sure there is a lot to improve here, particularly in the style files. I think it could be done in plain CSS with fewer lines of code. Any suggestions would be welcome. Thanks.

A couple of questions:

  1. What units you recommend for margin, padding, font-size, for such a project.
  2. For this project, is it better to use background-image CSS property or <img> element in HTML?
Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Adeel•55
    @asab07
    Posted about 4 years ago

    Thanks for your response, Vanza. It appears that rem units are more predictable than em units.

  • Vanza Setia•27,715
    @vanzasetia
    Posted about 4 years ago

    👋 Hi Adeel! My name is Vanza!

    I am going to answer your questions:

    1. I recommend to use rem units in any projects, since rem can let the user change their font-size. If you're using px, the user can't see any difference, which mean they can't control their font-size, based on their setting. For em, in some cases you can use it for padding and margin.
    2. I would argue, that using background-image is much better. The reason for that is because, it much easier to create purple effect just by doing this:
    .card__image {
      background-image: url('../images/image-header-mobile.jpg');
      background-repeat: no-repeat;
      background-size: cover;
      background-color: #aa5cdb;
      background-blend-mode: multiply;
      height: 14rem;
    }
    

    And then you can change the image into desktop version by adding media query. (also you can remove the img tag inside the card__image).

    That's it! Hopefully these answers your questions!

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

Oops! 😬

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

Log in with GitHub