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

Mobile first stats preview card using flexbox & media query

why-not-phoenix•300
@why-not-phoenix
A solution to the Stats preview card component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Hey guys,

Here's my solution for the stats preview card.

  1. Would've felt better making the side image a background-image but couldn't figure out the right blend with the background-color. I'd appreciate tips on how to mix images and colors.
  2. Main might look terrible on some devices, I tried fixing that, what do y'all think I could've done better?
  3. Wasted a lot of time trying to get the right dimensions. Is there an easier way of getting dimensions that fit?

My code might be messy, I'd appreciate any tip on optimization and better arrangement. Generally, I just need an assessment on these guys. Thanks for taking the time to help.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Faruk Abdulganiyu•380
    @faruking
    Posted almost 3 years ago

    Nice job. What I can add is that you change the width of the card(line 27 css) to 90% to get it closer to the design.

  • Vanza Setia•27,715
    @vanzasetia
    Posted almost 3 years ago

    Hi again! 👋

    Good job on this challenge! 👏 It looks similar to the design (judging from the design comparison).

    Regarding your questions.

    • You have done a great job with the image overlay. So, from me, there's nothing to fix since it already looks the exact same as the design. Great job! 👍
    • Don't change the html font size.
      • It makes the card looks small on mobile view.
      • It can cause huge accessibility implications for those users with different font sizes or zoom requirements.
      • If you are using a CSS framework, it can cause a lot of problems. All the sizes would be changed.
    • I recommend keeping it simple. So, the initial styling is a one-column layout and then uses media query to make the card has two columns. Currently, making the card as two columns on 1350px width is a little too late. Also, there's no need for max-height.

    For the m styling, you can make the "m" for "12m+" be uppercased on the HTML. It's just a single letter so I don't think it would cause any issues even if the screenreaders pronounce it as the letter "m".

    The statistic number should not be a heading. Just, use strong or use span and then make it bold with CSS.

    Hope this helps.

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