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

Stats preview card with grid and flexbox

Eero Liuska•60
@eerolli
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 using media queries. Could I have done this without them? Any other feedback welcome.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Ehtisham Ali•150
    @Ehtish
    Posted almost 3 years ago

    Hello Eero, Congratulations on completing challenge. You have done a great job with media query.

    Few suggestions if you don't mind:

    • For next project, I suggest, try to make your font size responsive with one line of code. how you can do this describe below:
    html{ font-size: 62.5%; }
    
    /* For mobile */
    
    @media(min-width: 480px){
    html{ 
    font-size: 55%;
     }
    }
    
    • To see much more details about this code click
    • Add live url to your readme on github. It will be very benefical to showcase your work.

    best of luck

  • David•7,960
    @DavidMorgade
    Posted almost 3 years ago

    Hello Eero, congrats on finishing the challenge! good job with your media queries, you landed it for the first time!

    Regarding your question, I think that for this project is necessary to use them, because you need to switch your grid from 2 columns 1 row, to 2 rows 1 column depending on the screen size.

    I would like to give you some suggestions for your solution:

    • Try using a <main> tag to wrap all the main content of your page (in this case, the whole card could be on a <main>), and then you can divide it through <sections> to give your document a more semantically meaning, with this you will get an improvement on accesibility and the search engines will position your page better!.

    • The styles I think that are fine, maybe making the card a bit smaller and setting the media querie for a less pixel value could make it look better, but this is just a tiny fix that you can take for future projects.

    Hope my feedback helps you, if you have any questions, don't hesitate to ask me! good job!

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

Oops! 😬

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

Log in with GitHub