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

CSS, HTML, Responsive Mobile and Desktop

Bao Nguyen•100
@quocbao19982009
A solution to the Stats preview card component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Hi, this is my first project on CSS and HTML as a web development beginner. Any feedback would be nice, Thank you. My problem during the project is the Unit, in order to get a responsive website I use units such as Percentage (%), vh, and vw. However, sometimes they do not give the outcome that I wish. Also, there is a lot of confusion regarding Max and Min (hight, width) use in CSS, is there any tips or document that you can recommend it would be very appreciated.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • hao pham•745
    @jerry-the-kid
    Posted about 4 years ago

    Nhìn tên có vẻ Việt Nam mà để Finland cũng ko biết tôi nên nói tiếng gì :)


    Ở 1000px -> 900px width là của ông bị vỡ là card nó bị quá width.


    1. 1000px -> 900px screen card oveflow Solution: @media (min-width: 798px) .card-content {width: 50%}

    1. 900px -> 800px screen data overflow : Solution : (ugly but fixed :V. Or you can decrease all font-size of card at 900px). @media (min-width: 798px) .data { flex-wrap: wrap;}

    1. 900px -> 800px picture not 100% height : You should set background-img instead of <img>

    Marked as helpful
  • Adam.Codes•180
    @AdamCodes42
    Posted about 4 years ago

    Hey, See if you want to make your website responsive try learning how max/min-width and max/min-height works it would be great and also maintain less code in your media query Example:-

    img{ width:500px; min-width:450px}

    So the img size won't be smaller then 450px

    • Arrange your css properly
    • I am also a beginner but as you complete your challenges you will get more improvement

    Happy coding 🙌🙂

    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