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

Responsive four card feature section with HTML/CSS!

bem
Luqman (Luke)•320
@luqmanx1998
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?

Another day another challenge completed !

This was another good, simple and fun challenge ! I'm proud of challenging myself by using grid, instead of flexbox, even though I instinctively knew how to use flexbox to do the layouts in both mobile and desktop, but I knew that it probably would be more fun to use grid instead, and I managed to do it so I'm happy about that.

Once again, something I would do differently next time would be to spend less time guessing the margins/paddings and spacings because it really does take a lot of time, and it's probably impractical to spend hours getting the pixels perfect. However, I am really happy with this result, I think I did even better than my first challenge so I'm satisfied :D ! I'm hoping someone would take a look and give me feedback again, that's the most exciting part !

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

I attempted this challenge using grid, something I'm not as confident with as with flexbox, however I knew I had enough knowledge to attempt it, and I'm happy I did ! I learned a lot along the way , made some silly mistakes with grid-rows but a moment of realization, and a facepalm was all I needed to correct those. I also spent quite some time trying to replicate that line break at the top, but I managed to learn how by reading an article on digitalocean, so in the end I really did learn something new !

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

Honestly, any feedback at all would be great ! It's really the most exciting part of all this, having someone to look at my work and review it would be amazing and much appreciated :D

On to the next one !

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on Luqman (Luke)'s solution.

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

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.