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

Four Card Feature

P
Will Cooley•200
@CooleyWC
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?

This was my first time using Sass for CSS

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

I know my box-shadow for the cards isn't quite like the Figma design - I could use help with this.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    David Lemvigh•200
    @dlemvigh
    Posted 6 months ago

    The visual

    Looks great, minor discrepancies from the design, but it feels more like a stylistic choises than mistakes.

    Nice use of CSS grid

    The code

    Nice clean HTML, the only petty comment is that you have multiple h1 headings which might not be the best for accessibility, but I could be wrong on that.

    The scss files are generally well structured. There is a bit of .hero styling that has snuck into _typography.scss which is confusion, and probably should be in _hero.scss.

    Marked as helpful
  • Robert Horosewski•310
    @horoserp
    Posted 6 months ago

    For the box-shadow, try drastically increasing the blur (to lighten the shadow) and adding a negative spread radius (to reduce its size).

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