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

Four Card Feature Section built with SCSS, Flexbox and Grid

sass/scss
P
Shakira Reid - Thomas•150
@KaeTheDev
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?

I’m proud that I was able to figure out how to get the layout working using flexbox. When I first saw this project, I kept skipping it because it felt like I needed to know just a little more about responsive design to complete it. Overcoming that challenge and getting it done felt really rewarding.

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

One challenge I encountered was getting the design to display correctly without scrolling on both desktop and tablet views. I had to dive into CSS Grid and learn how to incorporate it into the media queries to achieve the layout I wanted. This really helped me improve my understanding of responsive design. It's not perfect but I am learning.

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

Honestly, I’m still learning responsive design, so I feel like I could use help with almost every aspect. With each project, I find myself stepping outside of my comfort zone, but I’m learning as I go. I really appreciate any and all feedback to help me improve!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Daniel Ayeni•1,240
    @Dannimations
    Posted 5 months ago

    Firstly, GREAT job on the flexbox layout 👏👏👏👏 I know this project wasn't easy to figure out, especially with the transitioning between the mobile and desktop view.

    What i'd suggest (and what I do personally) is use wps photo viewer to see the full-screen version of the project and the image, and then alternate between them using the two by using alt+tab. That's how I do it, and I think that'll really help.

    Then for the screen sizes, just knowledge of media queries is kida enough to make progress on your own, especially if you like to experiment with different screen sizes.

    @media (min-width: 800px){} that's for the bigger screen sizes

    @media (max-width: 450px){} that's for smaller screen sizes.

    Hope this helps:)

    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

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