Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted about 1 month ago

Four-card feature section solution

antoni0kim•190
@antoni0kim
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?

This was first time I felt the solution came up quickly and noticed improvement on my CSS skill and felt good about the progress I made. If I were to start all over again, I would start writing the :root {} with variables before starting the project, instead of writing the variables at the end and modifying the codes.

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

The approach of setting the cards in desktop version. I knew I had to use some sort of grid, and I asked ChatGPT for help which I did not like the solution at all, because it was making it too complicated than it needed to be. The solution provided by ChatGPT suggest placing one of the card into second column, but that gave an idea of instead of placement, I would have three columns, and each column being in on container, except the second container having both team builder and karma card, and using flex to set the alignment. Modification on html was done to wrap them around in the container, and then placing the flex containers inside the grid was a hybrid solution that I decided to go with.

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

Because Figma was not provided, I had to eyeball the solution with the width and size of the card, so I would like some feedback on the dimensions. I'm also not sure if the breakpoint between mobile and desktop was done correctly; I decided that having 70rem of 15px was probably a good breakpoint, but if there's a suggestion as to how to go about this, I would like your advice on it.

The container display for flexbox also felt bit repetitive and I think there could've been better way to do this, but I decided to go with what works first, and optimize later. Now that I look back, it could've been just div class with "column" and modify all of them at the same time instead of repeating each of them individually.

I also don't think the shadow was done properly. I'm not sure how I can measure the shadow in the example and try to mimic the effect since there are many variables in play here.

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 antoni0kim'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
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.