Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted over 1 year ago

Responsive Stats preview

MarkPraise•150
@MarkPraise
A solution to the Stats preview card component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)
Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • Grace•32,130
    @grace-snow
    Posted over 1 year ago

    I'm afraid you need to change quite a bit in this. It's really important you learn to apply well structured meaningful html before moving on.

    1. The image half of the component should contain a picture element not just an img. The mobile img src should be the default and then the desktop image src goes in the source tag with a media query defined in rem or em.
    2. Look up how and when to write alt text on images. There is an excellent post about this in the resources channel on discord.
    3. The 3 stats in the component should be a list with 3 list items in it. Don't use span or divs only for text, you should always be able to use a meaningful element. This is a really important step to learn - translating designs into html is all about imagining the content separate to the design and choosing the most appropriate elements for that content.
    4. Don't style on IDs! That's not what they are for. Every ID must be unique on a page so you cannot use them like this for component styling. They also drastically increase css specificity so would create a nightmare managing styles in bigger projects. Use single class selectors for styling whenever possible. For more about what the ID attribute is I've written a full post about IDs
    5. It is better for performance to link fonts in the html head instead of css imports.
    6. Always use a modern css reset at the start of the styles in every project. Get into the habit of using it now. Andy Bell has a good one you can look up and use.
    7. Never limit the height of elements that contain text. You must change height 100vh to min-height. This will be causing a serious overflow bug in your code at the moment.
    8. The max width on a component must be in rem not px or %. This means it will work well for all users, including those who use a larger text size.
    9. Don't set height on this component. Let the browser do it's job and decide what height is needed based on the content. Remove all heights and widths in this. Only the img will need height and width 100% on desktop.
    10. You can place the border radius once on the component along with overflow hidden to crop out the overflowing child corners instead of setting it on individual child corners.
    11. To do the image colour that half of the card should have the violet background color and the img should have mix blend mode multiply and opacity 0.7.
    12. font-variation-settings is only applied to variable fonts. You don't need to add that or font-optical-sizing in this. You also don't need to set font style normal unless applying it to something that wouldn't be. It's already the default.
    13. ⚠️ Font size must never ever be in px. Use rem.
    14. Media queries must be defined in rem or em not px and you will never need to apply one at a small screen size like the equivalent of 375px. You only add a media query at the point where there is room for the layout to change. It's worth reading my post about media queries

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.

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