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

Four card feature section with CSS Grid and Flexbox

Ryan O'Hanlon•140
@Ryan-OHanlon
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?

What I'm most proud of from this challenge is that I'm starting to understand to make a responsive website will involve using both CSS Grid and CSS Flexbox.

Learning that you can use grid-template-areas and use periods to take up space on the grid is a neat trick for being able to place elements in a cross formation like in this challenge.

    main{
        display: grid;
        grid-template-columns: repeat(3, 1fr);
        grid-template-rows: repeat(4, 1fr);
        grid-template-areas: 
            ".team-builder."
            "supervisor team-builder calculator"
            "supervisor karma calculator"
            ". karma .";
        gap: 2rem;
    }    
What challenges did you encounter, and how did you overcome them?

The main challenge I encountered was learning how to implement both CSS Grid and CSS Flexbox at the same time. Having to design custom CSS rules for both mobile and desktop really makes designing and using HTML elements extremely complicated that you feel like you need to create multiple or elements to solve the challenge as both Grid and Flex involves being able to use attributes for a parent-child relationship.

The way I overcame this was to use Grid for the webpage design and use Flexbox for the content. This is the practice I would like to move forward with to develop my knowledge of both Grid and Flexbox.

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

The area I would like help from with this project is understanding how to stop the text and images from being responsive using CSS.

I know I try and make an exact match of each challenge, but I can't stop the text from being responsive when the window size increases or decreases as seen in the mobile-design and desktop-design pictures.

I would also like help with figuring how to figure out how big or small containers should be for each challenge. Because either I make them responsive or set a specific size and I don't know what's the best practice.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Tuna Erten•430
    @tunaerten
    Posted 12 months ago

    Bravo, your project looks great. I had done mine using flexbox, but you did an excellent job with grid as well. The colored borders on the cards end in a straight line; to achieve this effect, you can add a pseudo-element and use the background color of the cards. This way, you can get a result that is a bit closer to the original. Although this project is small, I think it would be more beneficial to work with class names. Lastly, when the screen width is around 1100px, the sections of the first and last cards are off the screen, so maybe you can think of a solution for that too. Congratulations!

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