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

Responsive layout for stats preview card

bem, sass/scss, webpack, node
MiloosN5•190
@MiloosN5
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'm intrested, since I've done this challenge with webpack, are @forward and @use valid? It didn't work for me, but @import does. In addition, any suggestion for better SASS organization will be helpful.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Randall3475•360
    @Randall3475
    Posted about 2 years ago

    Hello, the @use and @forward methods - as of now - only work in Dart Sass, which is the version of Sass that includes all newer features.

    More on Dart Sass here: Sass: Dart Sass

    Marked as helpful
  • Vanza Setia•27,715
    @vanzasetia
    Posted about 2 years ago

    Hi, MiloosN5! 👋

    I do not know about Webpack. But, Sass recommends using @use and @forward instead of @import.

    I wrote a blog post to help you write better Sass code. It contains five code snippets. They can help you write media queries, convert px to rem, and much more.

    5 Handy Sass Code Snippets — Vanza Setia

    Some suggestions:

    • Empty alternative text: Decorative image should have empty alternative text—alt="". If you write "..." (triple dots), the screen reader will still announce it.
    • Appropriate element: Use a list element for the statistic, <div class="stats__content__numbers">.

    If you want to get more feedback, I recommend using HTML and CSS. This way, more people can give you feedback.

    I hope this helps. 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
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