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

Stats preview card component Using HTML and CSS

Hamzat Lawal•560
@EngineerHamziey
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 Everyone, I just finished this project and all suggestions are welcome 😁 thanks

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

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

    Hi, Lawal! 👋

    In my opinion, the responsiveness for the site is a little more complicated than it should be. I suggest only having one media query for the mobile layout (it looks like you write the CSS for the desktop layout first).

    So, I recommend doing the following for the responsiveness.

    • First, I suggest only having one condition media query. It means that there's no need for the logical operators (and). In my experience doing Frontend Mentor challenges, I never write complex media queries.
    • Second, the site only needs one media query to be responsive. So, the initial styling for the desktop layout and the media query for the mobile layout. However, I strongly recommend writing the styling using the mobile-first approach. It often leads to shorter and better performance code. Also, mobile users won't be required to process all of the desktop styles.
    • Third, never limit the height of the body element. If you ever need to specify the hieght, use min-height instead.

    Those are three suggestions from me. In addition to those, I have some more feedback.

    • Use CSS to uppercase the text. The uppercased word in the HTML might be spelled by the screen reader (spelled letter by letter).
    • Always use single class selectors to reference all the elements that you want to style whenever possible. Using id is going to make your stylesheet have high specificity (hard to maintain). As a side note, ideally, id should be used for anchoring.
    • I suggest making the #lower-content as a list item. Also, swap the h2 with p instead. It's because if the site has no styling, it's more likely to be a list.
      • 10k+ companies
      • 314 templates
      • 12m+ queries
    • It's best to write HTML first without any styling. In my experience, it makes me decide on better HTML markup.
    • Also, you might find it helpful if you think of the HTML page as a document file. So, you can think of an h1 as a title and then h2 as a sub-title, etc.
    • On mobile view (375px * 640px), the card is too narrow. I suggest reducing the amount of margin on the .main-container element.

    That's it! 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