Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 22 days ago

Stats preview card component

bem
Tetiana•390
@TetianaAleks
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 specific areas of your project would you like help with?

I’d really appreciate any feedback on my solution, especially regarding code structure, accessibility, responsiveness, and user experience. Any suggestions will help me improve!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    Andrey•4,320
    @dar-ju
    Posted 22 days ago

    Hi, Tetiana!

    Awesome work!

    What I would change:

    • the picture is not just some abstract image or figures, it is a fully-content image. Content for a search engine can only be transmitted via the <img> tag with a description in alt. In more complex works, you will always need to ask yourself - is this a content image or just a decorative element? And then decide how to position it correctly
    • at a screen width of 760px, the block seems too narrow, you can remove the fixed width and make side paddings
    • the card__stats block is more of a list, use ul
    • there is an important point about the height of the blocks, use a fixed height very carefully. Imagine that there will be 5 times more text in the card - add it and check what happens. The text will simply go beyond the block. And your layout should be resistant to changes

    Otherwise, everything is great, keep up the good work!

    Marked as helpful
  • Yacoub AlDweik•3,110
    @YacoubDweik
    Posted 22 days ago

    Hey! good job!

    .card__content > .content__title and not .card__title

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

Oops! 😬

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

Log in with GitHub