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

Responsive 3-column card using CSS Grid & Flexbox

bem, pure-css, progressive-enhancement
Mohamed Djaballah•60
@Djabouex
A solution to the 3-column preview card component 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 the clean structure and responsive layout I achieved using CSS Grid and Flexbox. I carefully followed the original design and made sure the content adapted smoothly to different screen sizes using a mobile-first approach. I also focused on styling consistency using CSS custom properties.

Next time, I would improve the accessibility of the HTML by providing more meaningful alt text for icons and ensuring better semantic structure (e.g., using <section> or <article> instead of generic <div> elements for content blocks). I would also consider adding transitions to enhance user interaction further.

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

One challenge I faced was aligning the content and spacing across the three card sections to match the design exactly, especially for different screen widths. To overcome this, I used CSS Grid to create a consistent column layout and adjusted padding/margin carefully.

Another challenge was implementing hover effects with proper contrast and responsiveness. I resolved this by testing across various screen sizes and applying transitions using CSS variables for cleaner styling.

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

I would appreciate feedback on the following:

  • Semantic structure: Is my HTML well-structured and accessible?
  • CSS layout: Could the layout be simplified further or optimized for performance?
  • Accessibility: Any suggestions for better alt texts, ARIA attributes, or contrast improvements?
  • Design consistency: Do my color choices and spacing feel visually balanced across sections?
Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • marlar•110
    @marlar-tz
    Posted 12 days ago

    Hey Djabouex!

    • Semantic structure:

    Your code is well-structured and easy to read. I noticed that our solutions take different approaches and use different methods, which gave me a chance to learn alternative ways of tackling the challenge. Thanks to your clear comments, the code is very readable.The use of semantic HTML greatly improves accessibility, and the consistent indentation contributes to a clean and well-organized structure.

    • Design consistency:

    Your color choices and spacing are balanced across sections and visually appealing. Everything feels cohesive and thoughtfully designed.

    Good Job! Keep Going💪

    Marked as helpful
  • Harsh Kumar•4,190
    @thisisharsh7
    Posted 12 days ago

    Great job on this submission! 🌟 Your layout is clean, responsive, and visually appealing.

    👍 Highlights:

    • Mobile-first responsive design is well-executed.
    • Transitions on hover are smooth and enhance UX.
    • Clean separation of concerns between HTML structure and styling.

    🔧 Some suggestions:

    • Semantic HTML: Replace <div class="sedans"> etc., with semantic tags like <section> or <article> for better structure and screen reader support.
    • Buttons: Use <button> elements or add role="button" + aria-pressed when using <a> as buttons.

    🎨 Optional:

    • Add subtle transitions to card hover states (e.g., box-shadow or transform).

    Overall, a very good solution — happy coding!

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

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub