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

Stats card component

livana•40
@livlivana
A solution to the Stats preview card component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


My first attempt at Frontend mentor's beginner challenge.

Not the most concise code and there seems to be a gap between the image and the image-container that I'm not too sure how to get rid of. Please do let me know how I can better improve my code/any shortcuts or best practice that I take note of! Thank you :-)

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Oludayo DS•100
    @multidamsy
    Posted about 4 years ago

    Good job, however, you have to do some work on the view on mobile and tab. The layout gets disorganised as I shrink to smaller deevices

    Marked as helpful
  • Matt Studdert•13,611
    @mattstuddert
    Posted about 4 years ago

    Hey Livana, congrats on completing your first challenge! Did you learn anything new while working through it?

    For the image, you need to add display: block; to remove the gap at the bottom. It's a quirk with images whereby you often need to add display: block; because of that issue.

    Be sure to check out the accessibility report. At the moment, you're missing the alt attribute on the img element. This will make screen readers read out the file path, which isn't helpful. You can either add descriptive text in the alt attribute or if you feel the image doesn't add context to the content, you can leave it blank like this: alt="". That will ensure screen readers skip the image.

    Also, I'd say the numbers in the stats aren't headings. Instead, you could change them to span elements to style them differently. The fact you've used a list is great, as it is technically a list of stats.

    I hope that helps! Let me know if you have any questions 🙂

    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

Frontend Mentor for Teams

Frontend Mentor for Teams helps companies and schools onboard and train developers through project-based learning. Our industry-standard projects give developers hands-on experience tackling real coding problems, helping them master their craft.

If you work in a company or are a student in a coding school, feel free to share Frontend Mentor for Teams with your manager or instructor, as they may use it to help with your coding education.

Learn more

Oops! 😬

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

Log in with GitHub