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

Responsive four card feature using Grid and Scss

sass/scss
P
Kumani Kidd•170
@amancalledkidd
A solution to the Four card feature section challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


What are you most proud of, and what would you do differently next time?

Using grid for the first time, I had previously mainly used flexbox. I will use it more often in the future, its a useful tool.

What challenges did you encounter, and how did you overcome them?

I had recently been learning about cube-css after watching the link provided in a previous section. However I found it hard to use as I didn't have a full understanding. I have applied some of the best practices but I ahve a lot more to learn.

Also find it challenging to know the best practices of semantic HTML, overcame this through reading more and trial and error.

What specific areas of your project would you like help with?

Best practices for naming classes?

Is my use of Scss nesting correct?

Any suggestions for improving this solution?

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    Gabe•320
    @gabei
    Posted 3 months ago

    Hey nice job!

    To answer your question about SCSS nesting:

    Usually the benefit of nesting in SCSS is the ability to append class names under the parent element. This is especially apparent when using a CSS methodology like BEM.

    For instance, if you had a paragraph tag with a .card__text class listed under your .card element, you might wright something like:

    .card {
       border: 1px solid black;
    
       &__text {
          padding: 2rem;
       }
    }
    

    This would output to:

    .card { styles here }
    .card__text { styles here }
    

    This can allow you to sort your CSS into a module-like arrangement, where all associated code is bundled together under a .card element at the top.

    Expanding on that idea is then quite easy:

    &__text {
       padding: 2rem;
       &--bold {
         font-weight: 800;
       }
    }
    

    outputs to:

    .card__text--bold { font-weight: 800 }
    

    And so on and so forth.

    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 1st-party linked stylesheets, and styles within <style> tags.

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.

Oops! 😬

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

Log in with GitHub