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

Frontend Mentor | Four card feature section

Dadir-Dev•200
@Dadir-Dev
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?

Before writing any code for this project, I took some time to plan my approach. I outlined how I wanted to tackle the challenge, identified the appropriate HTML elements to use, and thought through the class structure—especially which containers could share classes based on similar styling. This planning phase really helped me understand the problem more deeply and develop a clearer mindset for implementation. It’s a step I found incredibly valuable, and I plan to continue using this approach in future projects.

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

I decided to make the font sizes responsive without using media queries by using the clamp() function. Choosing the right minimum and maximum values, as well as the appropriate relative units, took some time since I had to test the layout across different screen sizes. But in the end, it was worth the extra effort.

One challenge I still haven’t fully overcome is layout alignment. I initially used display: grid for the middle cards, but I struggled to center the card container within the body. Eventually, I switched to display: flex, which worked better in this case. It made me realize that I still have room to grow when it comes to mastering CSS Grid.

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

Any feedback is welcomed and appreciated!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Kyle Parsotan•150
    @Kyl67899
    Posted 3 months ago

    Nice work on using the flex/grid layout and building the card using media queries and such. Nice work.

  • Andrej Trožić•90
    @AT95BL
    Posted 3 months ago

    This was a great challenge to work on! I found the instructions and design files to be clear and helpful. It was a good exercise for practicing my [responsive design skills, Flexbox/Grid layout, component building]. Thanks for providing such a valuable learning experience!

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.

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