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

Stats Card - Solution!!!

Daniel Ayala•290
@dan-ayalahdez
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 struggled to make both flex elements (The image and the stat info div) in the main div to be exactly the same size, is there an easier way to accomplish this?

Also, in this project i used em and rem instead of pixels as recommended by some of you, any tips regarding these units are highly welcome!

Thank you! :)

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • romila•3,550
    @romila2003
    Posted about 3 years ago

    Hi Daniel,

    Congratulation 🎉 on completing this challenge, it was a good attempt but there are some problems that I want to address:

    1. Regarding the responsiveness of the card, it is not very responsive when adjusting the screen sizes. The card looks fine in the desktop version however the mobile and tablet version does not look fit within the screen and display well. Thus, it is best to take a mobile-first approach so that it would be easier to adjust the elements as the screen increases. Also, it would be better to use the min-width instead of max-width.
    2. In the mobile screen size, I noticed some of your codes were quite long in css. Sometimes, it is easier to use the broader terms and type the elements there e.g. border-radius: 0.5em 0 0 0.5em; and padding: 1rem 4rem 2rem 4rem;. This makes it easier to shorten your codes. If you do not understand, the values follow as below:
    • top-left
    • top-right
    • bottom-right
    • bottom-left

    The design overall looks great and pretty accurate to the design provided.

    I wish you success with your future projects and keep 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

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