Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 20 days ago

Responsive card layout using CSS Grid, Flexbox, and semantic HTML

Diego•50
@diegobezerra80
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 am most proud of successfully implementing a fully responsive layout using both CSS Grid and Flexbox, which ensures the feature cards look great on all screen sizes. Next time, I would spend more time optimizing the typography and spacing with CSS clamp() and logical properties to better support different languages and text sizes from the start.

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

One challenge was balancing the use of CSS Grid and Flexbox together to achieve a clean and flexible layout without redundancy.

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

Any suggestions on advanced CSS techniques for responsive typography and layout flexibility would be very helpful.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Gavin•360
    @DesignAssembly
    Posted 20 days ago

    All in all a good solid effort, well done. Good use of grid and flex box, some small things is obviously getting the top headline and sub text to be same size as in design. in your 2nd and 3rd nth-child you could add: place-self: end; and place-self: start to close the center gap and get your gaps consistent. the border at the top has a curve obviously following, the radius. If your really want to be pedantic and fix little nuances like these might be better to add in a span for the color-bar with overflow: clip on the card.

    Other than that well done mate!!

  • Julian Balaguera•160
    @julianchoripan
    Posted 20 days ago

    very nice!

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, SASS, 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