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

Card feature section (CSS flexbox + grid)

Allan Sancley•130
@AllanSancley
A solution to the Four card feature section challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)
Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Khrystyna Horbenko•230
    @KristinaHorbenko
    Posted 9 months ago

    This is a very interesting solution for card placement. The chosen grid and responsiveness add structure to the design and make it user-friendly across different devices. However, it's worth paying attention to the fixed margins for images. In the CSS, the fixed margins for images (margin: 25px 0 0 200px; and margin: 30px 0 0 232px;) can cause issues with responsiveness. It would be better to use flexible values like percentages or rem for smoother scaling across various devices. Unoptimized CSS: There are many repeated styles for the article element. For instance, width, height, border-radius, and padding-left could be placed in a common class for all articles, which would reduce the code volume and make it easier to maintain. Lack of color variables: Color values (hsl(...)) are repeated multiple times in the code. Using CSS variables for colors would make it easier to change the color scheme in the future.

    Marked as helpful
  • collins-ai•450
    @collins-ai
    Posted 9 months ago

    Congratulations on your solution, the solution is looking almost like the original design. Semantic html like header and footer are present in your code which is very nice. The accessibility of the solution is also very good. Concerning the layout it looks ok in different screen sizes but in smaller laptops it doesn't fit properly.

  • manuel360•110
    @manuel360
    Posted 9 months ago

    Great layout cheers 🥂 my only problem was the box shadow it was only at the bottom of the card but apart from that 👌

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

Oops! 😬

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

Log in with GitHub