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

Stats Preview Card Component

Sae Matsuda•240
@SaeM843
A solution to the Stats preview card component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Hi there, I’m Sae and this is my solution for this challenge👋

I am strugglig with a media query. I am trying to centre the texts but as there are padding and margin inherited from a desk top version and it won't be centred. Your feedbacks are more than welcome!

Thanks:)

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Abdullah Ayoola•1,080
    @abdullah43577
    Posted about 2 years ago

    Hey there, I don't fully understand the issue with the code you said you're having, but I can suggest a fix as I got some key points out from the issue you highlighted, you're trying to center some texts and for some reasons on mobile screen sizes it won't center because of a padding inherited from the desktop screen version?

    if this is the issue, using media query could solve this issue, you could just use the media query to remove the padding instead or reduce the padding to achieve what you want and that should work.

    let's take this as an example: desktop version: .container{padding: 5px 16px}

    using media query, I can remove the padding from the container element completely or reduce the padding as I'd wanted

    @media (max-width:400px) {.container{padding: 2px 4px}}

    let me know if this did solve the issue you're having with your code. Happy coding.

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