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

responsive four card section using, sass-grid

sass/scss, accessibility
Tassie Oshiro•60
@tassieoshiro
A solution to the Four card feature section challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


I had a little difficulty moving the icon to the right of the card, still getting used to how to space the elements. Any criticism feedback is appreciated.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Miguel Silva•490
    @migsilva89
    Posted over 3 years ago

    Amazing work, congrats.

    I would add max-width from 1600px, cause if you go bigger the side cards are getting separated from the middle ones.

    For the rest looks perfect, well done!

    Regards, Miguel Silva

    Marked as helpful
  • Jordane Gengo•590
    @jgengo-alt
    Posted over 3 years ago

    Hello there 👋

    First of all, good job 🚀💣

    📋 To position your images to the card, the simplest way to me would have been to actually add a position: relative to your container-cards__card div, and then add a position: absolute; bottom; 2em; right: 2em to your img. In a nutshell, by doing that you are positioning your card with absolute value inside the relative space of your card.

    📋 Everything looks extremely huge from my screen, as another peer mentioned a max-width would have been a good addition. 🔥

    📋 Another point you could have re-use your grid with the mobile view, just by changing the grid-template-columns: 1fr .

    📋 Also, with your grid I see you using some margin I would suggest using the gap or grid-gap :)

    Once again! Good job 💪

    Keep going 🌱

    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