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

four card project using SCSS

sass/scss
P
V.S Karthik Tirumalasetty•130
@VSKarthikT
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 particularly proud of how I utilized SCSS mixins to create reusable styles, such as flex layouts and centralizing the border color styles for each card. This approach significantly improved in reducing generated CSS code , allowing me to make layout changes efficiently across the project.

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

I struggled with aligning elements in the desktop layout, especially when positioning elements like .super_container and .calc_container to stick to the left and right edges while keeping the middle elements centered. This alignment was difficult to achieve within a single flex container due to the varying content sizes, which made the elements misalign or fail to stretch evenly. To address this, I added wrappers (wrapper_super, merge_box, and wrapper_calc) around certain elements to create individual flex containers. This allowed me to control the alignment and distribution of each section separately. By combining justify-content: space-between with media queries, I was able to create a responsive desktop layout that aligned as desired.

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

While the current layout works, I feel there may be more efficient flexbox techniques or grid approaches to achieve the desired desktop layout without as many nested wrappers. Any guidance on optimizing complex responsive layouts with fewer containers would be helpful. I’d appreciate tips on maintaining equal height for flex children in a row without relying on fixed height or min-height. Sometimes, flex children with varying content height still misalign slightly on different screens, and I’m looking for more flexible ways to solve this.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Bruno514•100
    @Bruno514
    Posted 9 months ago

    Very nice layout! I actually used grid and didn't even think this challenge was possible using only flexbox...

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