Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 8 months ago

Responsive Flex Stats Card with Sass

sass/scss
IO•720
@i000o
A solution to the Stats preview card component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


What are you most proud of, and what would you do differently next time?

I'm proud of my comfortability with these layouts now. While I still face some challenges, I'm confident approaching them and trust that I can make a good quality, responsive design.

I think I'm over the mobile-first workflow. It tends to make me underestimate how much work there is to do in the desktop version (even if it's not much), and I don't plan my HTML as well as I could. I enjoyed a desktop-first approach when I started out with it, so I might revert back. I also mainly navigate sites on desktop, too so I think as a user it makes more sense to me to design this way. I'm open to changing it again in future, though.

What challenges did you encounter, and how did you overcome them?

I wasn't able to make the blend-mode on the image card match the design. I felt like I got close but couldn't figure it out, even with research. I used blend-mode properties and opacity to get this close, but it's still too dark.

What specific areas of your project would you like help with?

I'd like feedback on my Sass, if there's anything I could add/adjust. I'm comfortable writing it, but I don't think I'm using it to its full potential. This is mostly because I don't always know what the project will entail so I don't make intentions to necessarily create mixins or variables as readily. (Also my documents are pretty short at this stage, still.) I namely just use nesting without thinking about it too much, which I enjoy.

  1. Please help with the image filter and how to make it match the lighter design.

  2. Please also help with the tiny gap underneath the image in the card. I couldn't figure out how to remove this and I think I've been able to in the past with similar briefs but I couldn't in this instance! It must be simple?

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on IO's solution.

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.