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

Stats preview card with grid and responsiveness (sort of)

Giovanni Beccaro•160
@Gioltek
A solution to the Stats preview card component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Hello! This is definitely my worst attempt at a challenge, I don't really know what happened to be honest, it was a mix of frustration about box sizes, background image not showing and responsiveness adjusts. It turned out in the end, but the code is messy and I even gave up giving the proper blend mode to the image (I could've probably sorted that out, but I was really done with it). May I ask you how do you work with projects like this, where the target resolution is 1440p, but you have a 1080p monitor? How do you "simulate" the differences while coding? I can see that my proportions are right, but I'm on a different resolution device so how can I know what the difference will be on 2K? I saw a video about the "clamp" element, I will try to use it in the next responsive challenge, what do you think of it? Is it helpfull? Thanks for reading and happy coding!

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • Aleksandra•360
    @alexattt
    Posted over 3 years ago

    I am not sure whether you have tried this...but :) You can simulate responsiveness of your web app and change dimensions of the possible screen, by right-clicking in your page, then "Inspect" and in the Devtools tab, which opens, on the top left you will see small phone/tablet icon, if you hover over it says Toggle device toolbar. Click it, then on your page, on top you will see a toolbar, choose dimensions: Responsive and then you can change your dimensions both manually and also below this toolbar you can click on different pre-defined dimensions, for example, Tablet - 768px, Laptop - 1024px, Laptop - 1440px etc. Despite the difficulties you faced, your solution looks nice anyway!

    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.

Oops! 😬

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

Log in with GitHub