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

Responsive preview card component using HTML and CSS

LiBee•370
@Li-Bee
A solution to the Stats preview card component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Here is my attempt at the stats preview card. Feedback is welcome on both the responsive design of the component and the code.

Would be interested in seeing what other people did with regards to getting the purple overlay over the picture (i did it using linear gradient).

Also would be interested if anyone had an alternative way in doing the stats and the spacing, i used CSS grid.

Lastly i got the component card height in mobile design to match by adding a bigger margin bottom to the queries element - did anyone do anything different? Was this the correct approach?

Thanks all!

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 3 years ago

    Hi @Li-Bee

    I'm afraid the html on this needs changing, it doesn't make sense at the moment and would have a really bad effect on assistive tech and search engines (might be useful for you to read too @darryncodes)

    • a header element doesn't go inside main, it's a separate landmark. Technically you can have headers and footers inside articles, but assistive tech users generally dislike that as it clutters up what is announced to them on the page and can be confusing when using landmarks to navigate.
    • similarly article doesn't make sense for only part of this content. If using article it needs to be the whole component, heading, text and image. They all belong to the same one component.
    • if announcing an image as valuable content like you are doing here never use a div, use an img element, that's what it's for. The image should be in the html if it's deemed meaningful.
    • by using css grid for the stats you've broken their meaning. Each number-word pair needs to be read together, which means they need to be in the same meaningful element as each other. The best semantics I can see for this content would be acheived by an unordered list containing 3 list items. Inside each list item the number can be wrapped in a span or strong tag set to display block via a class. That means you wouldn't be able to use grid as planned (annoying I know)

    Layout-wise I'm seeing a few strange things viewing on mobile (ill add Screenshots to slack so you can see what I'm seeing)

    • the card is touching screen edges. Usually you mitigate against that with some padding on the outer wrapper, or you could add a little margin on the component itself
    • the card is showing up about halfway down the screen on page load. That just looks strange
    • on mobile landscape the view has switched to desktop layout already so the image becomes all squished. Make sure your media queries kick in at the point where there is room for the layout to change

    I hope this helps ☺

    Marked as helpful
  • darryncodes•6,350
    @darryncodes
    Posted over 3 years ago

    Hi LiBee,

    Your solution looks really good - well done on this one!

    • you've almost got the purple overlay perfect. i'd remove the opacity on the linear-gradient background-image: linear-gradient( to right bottom, rgba(170, 92, 219), rgba(170, 92, 219) ) and add background-blend-mode: multiply;
    • grid was a good choice for your stats layout, nice one. Gap is a really useful option whilst using Flexbox but you just need to be careful as it's not adopted by all browsers yet
    • you could clear up your accessibility report if you change your <section> tag to a <main> tag and use <article> or a <div> for where your <main> tag is now

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

Oops! 😬

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

Log in with GitHub