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

four card feature section component

Utkarsh9571•640
@Utkarsh9571
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?

it took a day, but i completed this project with css grid the way i want, i made a silly mistake because of that i need to watch some videos but i didn't like their approach, maybe they are experts and their approach is better, but i want to do it in that way i did.

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

It's funny, i created the div elements and a main but only added the material in one div, all other three divs were empty and i bashed my head for 4 hours, that what is the problem, why after creating rows and columns only one cell has material, and other cells were empty and the materials are floating outside, eventually i found that, and corrected it.

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

can someone go through my previous projects, i think their is a better way to center everything, i don't know why but every other project i open and did the same thing from previous projects, it won't work in current one, it just won't go in center, and then to complete the project i will have to mannually center it by either margins or position:relative feature.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    Kyle Mulqueen•400
    @kmulqueen
    Posted 3 months ago

    The desktop design looks great! However, I noticed two main issues that are affecting your responsive implementation:

    Your mobile layout has horizontal overflow causing content to extend beyond the viewport. This is primarily due to the fixed min-width of 1200px on your .container class. In responsive design, avoid using min-width with large pixel values as they prevent proper scaling on smaller screens. Regarding your centering struggles: I see you're using both place-content: center and justify-items: center on the body, which is good, but your container's fixed dimensions are overriding these centering properties.

    Some specific suggestions that may help:

    • Replace min-width: 1200px with max-width: 1200px in your .container class.
    • Add width: 90% or similar percentage-based width to .container.
    • Consider implementing a proper tablet layout between 768px-1100px.
    • For the card images, replace the absolute positioning (left: 12em) with flexbox alignment.
    • Use margin: 0 auto instead of fixed margins to ensure consistent centering.

    These adjustments should resolve both your mobile overflow and centering issues without requiring manual positioning.

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