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

Four-card-feature-section Responsive

Rod•90
@RodRyan19
A solution to the Four card feature section challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Hi! I would love to hear some feedback if there things I did wrong.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Venus•1,790
    @VenusY
    Posted over 1 year ago

    Hey! I had a look at this project as you requested, and it's really good! Almost no issues at all from what I can see.

    The site is responsive, and it resembles the design very closely.

    The only thing I would suggest is that you should consider using padding instead of margin for the whitespace around the edges of the page.

    This is because using margin makes it so that the site has scrolling at all times, even if the user's screen size is tall enough to fit all the content.

    Using margin causes this issue because it's not considered in the calculation of the element's width or height, even if the box-sizing is set to border-box.

    border-box only includes padding and border as part of it's width or height.

    So this in combination with min-height: 100vh means that the height of the webapge is always going to be 100vh + whatever the margin is, causing the scrolling issue.

    I hope this explanation has been helpful, but if not, please feel free to ask me questions, and I'll try my best to clarify.

    body {
      margin: 2rem; ❌
      padding: 2rem;
    }
    
    @media screen and (min-width: 800px) {
      body {
        margin: 4rem; ❌
        padding: 4rem;
      }
    }
    

    Other than that, you did a fantastic job at this challenge, and I can see that you're improving a lot! :)

    Marked as helpful
  • Olaniyi Ezekiel•7,580
    @Ezekiel225
    Posted over 1 year ago

    Hello there 👋 @RodRyan19.

    Good job on completing the challenge !

    Your project looks really good!

    I have a suggestion about your code that might interest you.

    📌If you don't have the Figma design files, I recommend using a browser extension called Perfect Pixel.

    It allows you to compare your finished project with the design images that come along when you download the project and check the (almost exact) dimensions. It's very useful!

    I hope this suggestion is useful for future projects.

    Other than that, great job!

    Keep up the excellent work and continue to challenge yourself with new projects. Your progress is impressive, and each project is a step forward in your front-end development journey! 🚀🌟.

    Happy coding.

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