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

Four card feature section

P
jeffgrahamcodes•260
@jeffgrahamcodes
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 how well the design aligns with the provided mockup and maintains responsiveness across various screen sizes. The use of semantic HTML, including <section> for the cards and <main> for the content wrapper, ensures accessibility and a logical structure. Setting a max-width on the .cards container was an effective solution to keep the layout constrained to three columns on larger screens, preventing the cards from overflowing into a fourth column. This decision maintained the intended visual hierarchy and ensured the design remained visually balanced.

Next time, I would focus on further optimizing the layout for tablets or intermediate breakpoints, where the design could use some fine-tuning to avoid large gaps or excessive spacing. Additionally, I’d explore adding subtle animations or hover effects to the cards to enhance interactivity and user engagement. Refining the accessibility features, such as providing descriptive alt text for the icons, would also improve the overall usability of the page.

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

The main challenge was ensuring the number of columns in the .cards section remained consistent across larger screens. Without a max-width, the flexbox layout defaulted to four columns, which disrupted the visual balance of the design. By setting a max-width on the .cards container and ensuring proper wrapping with flex-wrap: wrap, the issue was resolved, keeping the layout visually cohesive. Another minor challenge was maintaining spacing and alignment for cards that required staggered positioning, which was overcome by using transform properties on specific cards to achieve the intended design. These solutions demonstrate a thoughtful approach to layout management and responsiveness.

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

’d appreciate feedback on a few key areas of the project. First, while the max-width on the .cards container resolved the issue of maintaining three columns on larger screens, I’d like suggestions on alternative approaches to handling column layouts and wrapping more efficiently with CSS. Are there better ways to achieve this using grid or modern layout techniques?

Additionally, I’d welcome input on improving the design for tablet-sized viewports or intermediate breakpoints. Ensuring the layout feels proportional and balanced on screens between mobile and desktop sizes can sometimes be tricky, so advice on fine-tuning these transitions would be helpful. Lastly, feedback on adding subtle interactivity, such as animations or hover effects, to the cards to make them more engaging would be greatly appreciated. Let me know if there are any other best practices I could implement to enhance the project further!

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • vamshi•540
    @VamshiReddy143
    Posted 6 months ago

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