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

stats-preview-cards using Flexbox and other CSS custom properties

Christ Kevin Touga Watat•270
@Christ-Kevin
A solution to the Stats preview card component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


I have some questions about my challenge. I recognize that I still need to make progress in responsive design and responsive images using CSS and I have some questions concerning these topics. The first one is rather vague and general. Can you please tell me how you have improved your responsive design skills? In fact I'm curious to see how you have progressed in this domain and if you have any tips to share with me in the field of responsive design and responsive images. The second question is about the site I just shared. Indeed I would have liked to have a media-query with "min=540px". But unfortunately it was not possible because when I reduced the window below 750px, the flex on the bottom left of my container did not have enough space. Do you think it's not a problem if my media querie is set to "min=750px" instead of "min=540px" as i did? Or do you think I should consider reducing the font size of this flexbox? Or do you have an alternative solution? Thank you in advance to all the team. Thanks frontendmentor

Translated with www.DeepL.com/Translator (free version)

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • ViyanMd•0
    @ViyanMd
    Posted over 3 years ago

    Hi there! I am not an expert, but here's what worked well for me:

    1. Watch some Kevin Powell Youtube videos on responsiveness, layout and css units and media queries.
    2. Start with something simple. I am talking about literally practicing with one div or img, then combine an img and a div, the add some text. On each step make sure elements behave exactly how you want.
    3. As soon as you feel comfortable with something really simple, you can go ahead and start newbie challenges here.
    4. In programming curiosity is the key. You can ask Slack community for css resources and just go article after article. In most cases authors use simple examples to demonstrate what they are doing. After reading an article, try to repeat it by yourself without looking at the author's code.
    Marked as helpful
  • Daniel Chettiar•140
    @dannyboi07
    Posted over 3 years ago

    Hey Kevin. I'm pretty new to this stuff too. Just a couple of weeks back I was absolutely dumb at layouts and general css. Content from YT creators like Kevin Powell got me going the right track.

    I recommend that you try the below link, from freecodecamp and Kevin Powell on Responsive web design. It's the basics. But Kevin explains the reasoning behind why he chooses certain things when he creates the layout, which I think is the best thing to learn from this video.

    https://www.youtube.com/watch?v=srvUrASNj0s&t

    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

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