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

Responsive Four Card Feature Section using CSS Grid & Flexbox

Dias•140
@adambeckercodes
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 most proud of successfully implementing a responsive layout for this project. The design adjusts well across different screen sizes, ensuring a consistent user experience on mobile, tablet, and desktop devices. It was satisfying to see how well the grid layout came together in the final product.

Next time, I would plan the layout structure more thoroughly before diving into the code. While the solution works, I believe a more detailed layout plan could streamline the development process and potentially reduce the need for rework. I’d also like to explore using clamp() for responsive typography to make the text size transitions smoother.

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

This was my first time building with CSS Grid, and the layout presented some tricky challenges. Specifically:

  • Positioning the cards accurately while maintaining responsiveness was challenging at first.
  • Understanding how to use grid-template-areas and grid-template-rows/columns efficiently took some trial and error.

To overcome these challenges, I referred to MDN Web Docs and practiced small, isolated grid examples to better understand how the properties worked. Breaking the layout into smaller sections and tackling them incrementally also helped simplify the process.

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

I’d appreciate any suggestions on:

  • Improving the efficiency and readability of my CSS Grid code part.
  • Optimizing the @media rules to make them more concise and scalable.
Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Kedar Gavali•670
    @Kedar37
    Posted 7 months ago

    perfect!

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