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

Stats Preview Card using CSS Flexbox

Anosha Ahmed•9,300
@anoshaahmed
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 would appreciate constructive criticism.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Julian Krüger•100
    @juliankruger
    Posted over 3 years ago

    Hi Anosha,

    there is not really much to criticize, this looks great! One thing you could add to really get the color of the image right is a pseudo-element. An ::after or ::before css-class that sits right above the image with the same background-color and a low opacity.

    Another suggestion for future challenges: The design works perfectly on the two screen sizes set by the challenge, but in between it is not responsive anymore. What might help is mobile-first approach. Design it for mobile screens first and then later add the complexity of the desktop design. The dev tools of your browser help displaying all the screen sizes. I would not rebuild this just for that, though but maybe keep it in mind in the future.

    A nice free course for that is Conquering Responsive Layouts by Kevin Powell. It takes 21 days and only presents you a very small challenge each day including some break days.

    Hope that helps!

    Greetings

    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 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