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

Responsive card component using both flexbox and css grid

NadiaFr•310
@NadiaFrShLm
A solution to the Stats preview card component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


It looks like my css file is huge, still can't understand how to minimise css proprieties.

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • Md Raihan Alam•520
    @Md-Raihan-Alam
    Posted about 3 years ago

    First of all, there is nothing wrong with having a big CSS file. Second, remove all comments and keep the necessary ones, it's a bad habit to have so many comments in one file. Third, You do not have enough knowledge about rem yet practice some more because I do not find your site responsive on my PC. Fourth, you can check this video to understand when to use CSS unit ->https://www.youtube.com/watch?v=N5wpD9Ov_To.

    As a suggestion, you can use percentages to make your content responsive. I use percentages mostly in width to make my content responsive.

    Marked as helpful
  • Ciceron•940
    @MarcusTuliusCiceron
    Posted about 3 years ago

    Hey, happy to see a fellow french citizen here :) However I'll stick to english for the sake of everyones understanding.

    There is nothing wrong about your css file size. it is not that big. You simply can't afford to not use the css properties you need. if you want to reduce your file size you will have to increase the number of file you have. This is usually a good practice when the layout to implement become richer. Another thing you can try is learning Sass, it's very close to css but have some extra features that in some case can reduce the size of your css (loops, conditions, nesting, etc)

    Hope this will help you

    Have a good day :)

    Marked as helpful
  • Ali Ahmed•680
    @Dany-GitHub
    Posted about 3 years ago

    I suggest to use css variables and u can expand your knowledge more by learning pre processor as sass or scss u will learn things as mixin , functions, extend, partials and more it will make your CSS short and u dont have to repeat so much stuff over and over, 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, SASS, 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

Oops! 😬

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

Log in with GitHub