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

Stats Preview Card Component with HTML and CSS

Sebastien•55
@SebastienPJ
A solution to the Stats preview card component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


All feedbacks are welcomed. This was my very first project without instructions and, although I am elated at what I came up with, I know it it full of errors. Had a very hard time with the positioning at first but started clicking and things started moving relatively to where I wanted them to. Will keep trying for better next time.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Raymart Pamplona•16,040
    @pikapikamart
    Posted about 4 years ago

    Hey, good work on this one and congrats to your first solution here! The layout in desktop is though, though I had to zoom out or used the scrollbar at the bottom and as I can see you did not make any mobile breakpoint.

    Suggestions would be that:

    • As you can see, there is this white space in around the content right. You could remove this by adding margin: 0 in your body tag.

    • There is this scrollbar at the bottom which we really want to avoid whenever we design something. This was caused by the width: 1440px on the .main-background selector, for some users who have wide screen this won't occur, but for others like me, it will. To fix, simply remove the width: 1440px declaration on it, then you could just add that as a max-width.

    • You could make use of h1 on your "Get insights that help your business grow." title since it make sense to make it a heading right. Just for making more semantic markup.

    Only those, but please consider making the mobile layout okay. Whenever we submit solution, always consider submit it full. So that we, other FEM lovers, could give you more feedbacks about the overall layout.

    But still, great work on your first solution here^

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