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

Responsive page using flex

Juan Galvez•50
@Galvez121
A solution to the Product preview card component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Could anyone explain to me why the justify-content: center; and align-content: center; did not center the page? I had to use margin: auto; to do so. I could take those lines off, and It will not affect the page layout.

For the responsive, I was not sure how to change one picture to another one. I did it using display: none. Is there any other way to do that?

Any comment that would help me to improve is welcome!

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

  • SuperJulia2024•220
    @SuperJulia2024
    Posted over 1 year ago

    Hi Juan,

    As Ahmarlftikhar has mentioned, you have to set the height of the container to 100vh in order to give some "space" to your main div so it can center in the page. Once this is done, you have to set "justify-content" to center and "align-items" to center (NOT align-content ! Align-content only takes effect on multi-line flexible containers, where flex-wrap is set to either wrap or wrap-reverse. A single-line flexible container (i.e. where flex-wrap is set to its default value, no-wrap) will not reflect align-content).

    To make your images responsive you have to use media queries. For example:

    • For mobile screen:

      <img src="./images/image-product-mobile.jpg" alt="Product picture" />
    • For desktop screen: @media (min-width: 1200px) { img { content: url("./images/image-product-desktop.jpg"); } }

    I hope it helps !

    Marked as helpful
  • AhmarIftikhar123•660
    @AhmarIftikhar123
    Posted over 1 year ago

    assalamoalaikum! set the height of container(body) to 100vh. for changing image at different seceen use picture tag inside it use source to change the image at different screen .also you can do this by js.

    Css: body{ min-height:100vh; }

    HTML: <picture> <source media="(min-width: 1024px)" srcset="large-image.jpg"> <source media="(min-width: 768px)" srcset="medium-image.jpg"> <img src="small-image.jpg" alt="A responsive image"> </picture>

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 1st-party linked stylesheets, and styles within <style> tags.

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.

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