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

Four Card Feature Section using Flexbox

sass/scss
P
kephalosk•400
@kephalosk
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?

n/a

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

Fine-Tuning the box-shadow by trying out different values. Ended up with: box-shadow: 0 12px 22px -8px rgb($color-grey, 0.8);

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

n/a

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    Scott•310
    @ldg
    Posted 6 months ago

    Hi Kephalosk,

    Nice work on this challenge, your Sass is so well organized I enjoy reading through it.

    Your flexbox solution works really well on phones and desktop, however on tablets it doesn't seem to work as well. I notice you solve the layout problem on larger screens by wrapping the Team Builder and Karma cards in their own content container so they stack once the cards have enough space.

    This works great on Desktop, however on tablets in portrait mode the layout seems to break. If you change

    .content { 
    flex-wrap: nowrap;
    }
    

    That would fix the layout, but squish the size of the cards. So not a useful solution. I'm not sure how to resolve that with flexbox.

    I'd suggest looking at Grid CSS for this kind of problem, you have greater control over the cards with Grid, so you wouldn't need to wrap those two cards to get them to stack.

    Either way, solid work on this challenge.

    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