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

Using the display grid and @media for this challenge.

accessibility
Stalin•410
@StalinAM
A solution to the Stats preview card component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


This is my solution for this challenge, I have a question: Is the div used correctly for the container and the ul tag? Any advice you can give me to improve it would be appreciated.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Lucas 👾•104,160
    @correlucas
    Posted almost 3 years ago

    👾Hello Stalin, congratulations for your new solution!

    🎯 Your solution its almost done and I’ve some tips to help you to improve it. If you want to add the same effect of the design for the image overlaying it with purple there's a shortcut that is by using mix-blend-mode with the mode multiply and with an opacity around opacity: 82%. See the code below:

    img {
    mix-blend-mode: multiply;
    opacity: 82%;}
    

    Use a CSS reset to avoid all the problems you can have with the default CSS setup, removing all margins, making the images easier to work, see the article below where you can copy and paste this css code cheatsheet: https://piccalil.li/blog/a-modern-css-reset/

    ✌️ I hope this helps you and happy coding!

    Marked as helpful
  • Leo•440
    @Souicia
    Posted almost 3 years ago

    Hello Stalin,

    Congratulations on completing this challenge! It looks really great and is responsive.

    There are some parts that could be slightly improved. First of all, you could have declared font-family 'Inter' in the :root pseudo, that would have made your CSS DRYer. If you need to change font-family further down the line, just redeclare font-family with another one on the class. Also, I think you should have customized your information container with a display flex, that would have enabled you to use the gap property and remove the amount of margins you declare. Continuing on that, you could have used margin: 0 auto to center the div, calc function on width to give it padding on the side. That would have enable you to delete your paddings on the children. Another thing, if there is only 2 elements within a div, for instance your information-container and the picture container within your main, I would use flexbox, not grid. Then you can just change the way elements are displayed with flex-direction, I believe it makes it easier. Last point, you may want to play with min and max width, to make it a bit more responsive to screen sizes, but that's just a bonus.

    All in all, your solution is concise, nicely written and works well, so once more, congratulation! Have a great day! :)

    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