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

Html5, Css3(flexbox and media queries)

Aastha Anand•345
@aasthaanand123
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 would appreciate if you all suggest me ways to improve my code since I really faced difficulties in applying the background color and at last took a shortcut(not using css) and also I faced certain problems in media queries and I'm not really sure if its written in a correct manner.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Tereza•605
    @sirriah
    Posted about 4 years ago

    Hello,

    Nice work. I have some suggestions:

    • Not everything should be in div tag. For example for paragraphs use p tag, etc. Look at some articles or videos - list of all tags and FreeCodeCamp - semantic HTML
    • Try to use BEM naming or another naming standard. This project is small, but If you will work on something bigger, you will get lost. [Video about BEM] (https://www.youtube.com/watch?v=SLjHSVwXYq4)
    • As josuke0227 mentions above - the responsiveness is not good. Try to add another breakpoint. I know that in the starter files are only designs for mobile and desktop, but It would be better, if the page will be visible in all devices. [Responsive design] (https://developer.mozilla.org/en-US/docs/Learn/CSS/CSS_layout/Responsive_Design) Your browser will help you with the media queries [Responsive design mode in Firefox] (https://developer.mozilla.org/en-US/docs/Tools/Responsive_Design_Mode)

    Have a nice day :)

  • SukiyakiFiend•115
    @josuke0227
    Posted about 4 years ago

    Hello, Aastha!

    Good work, mate👍

    What I'd like to suggest is as below:

    1. You can apply font-style globally if you set it to body in your stylesheet.
    2. The break point which the layout is switched to desktop one may be a bit too small since the left side of the contents is outside of the screen.

    I hope it helps.

    Happy coding! :)

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

Oops! 😬

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

Log in with GitHub