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

Four Card Feature Section Built With HTML/CSS

Dylan•290
@dquinn089
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 am most proud of how I utilized flexbox and grid styling to simplify the code for the layouts between the different types of displays. Having control with these properties makes it so much easier than having to manually adjust the positioning of elements with padding and margins. The one thing I would do differently next time would be to use elements for the cards instead of ``s just because the code for the styling would have turned out so much cleaner. I will most likely update this in the future.

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

Having to understand the fundamentals of flexbox and grid was the biggest challenge. It was nice to have the help of some beginners guides to understanding these properties, but it was a challenge in of itself to test the different properties for this specific project. Though it was time consuming at first, having the knowledge of how to utilized these properties will for sure be much more efficient than adjusting each individual element.

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

Since the start of using flexbox and grid, I feel that I am still overcomplicating the properties. Although my code seemingly gets the job done, I feel as if the same output could be executed with much fewer lines of code. Any tips I will take!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Alex•3,130
    @Alex-Archer-I
    Posted about 1 year ago

    Hi!

    At first I like this hover effect - it's smooth and cool =)

    I can't see where you are overcomplicating with grid. Maybe using auto for middle column - guess it's more neat when all the cards keeps the same width. But that isn't a big deal =)

    A bit grumbling about semantic - it's a list of the cards =)

    Oh, and you mistyped a bit - display: flexbox instead display: flex. That's why flex doesn't work on the mobile screen. By the way, you also can change grid to grid-template-column: 1fr just to avoid adding new properties.

    So, great work, congrats =)

    Marked as helpful
  • Owolabi•250
    @Ay-dotcode
    Posted about 1 year ago

    Nice job 👍

  • YADAV0057•120
    @YADAV0057
    Posted about 1 year ago

    did you forget to color your cards?

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

Oops! 😬

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

Log in with GitHub