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

Four Card Feature Section (Resaponsive)

surpoxia•120
@surpoxia
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 think when it comes to the MockUp, I am pretty close.

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

My biggest problem was the responsiveness. My site now works as was demanded, but I wish it would behave more fluidly and organically when you resize it. I know it is possible even without a Media Query and by just using the grid layout alone, to make the grid just change its layout as you resize the page.

Right now my CSS is a bit of a mess, because of all the adjustments I needed to apply to the Media Query for the mobile version of the page. And when you resize it, it just snaps into into its nerw layout. I wish it would do it more smoothly.

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

Maybe someone could explain to mehow to make the grid grow and shrink and change it's layout when resizing the page more smoothly, when you start out with a complicated layout like in this challenge.

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

  • Jeje•2,050
    @AkoToSiJeromeEh
    Posted about 1 year ago

    Hey ! Great Work out there i just notice that the four card component is does not vertically align on the middle ( you can notice it by zooming out the web page ) you are correct through the usage of flex with the properties of justify in order to center the component but the reason why its not vertically align is because there are no height it is very important whether you want to center something. by adding this on the body you can achieve to vertically align the component . that's all happy coding !!

    body {
      display: flex; // add this
      flex-direction: column;
      justify-content: center; // add this
      margin: 0 auto; //remove this since you are using flex properties
      background-color: var(--Very_Light_Gray);
      align-items: center; // add this
      min-height: 100vh;// add this
    }
    
    Marked as helpful

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