Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted almost 2 years ago

CSS Grid and Flexbox product landing page

SonEfAdam•10
@SonEfAdam
A solution to the Product preview card component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


  • I realised that my CSS, especially flexbox and css grid, is not really that good. How can I use them in a better way? I always find myself guessing random pixel numbers for the font sizes or grid sizes.

  • The bottom of my image element is not really touching the box that I made. I am not quite sure how to fix this.

I am still very new to HTML and CSS. I hope you guys can provide good feedback for me. Thank you!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • the-coding-beekeeper•270
    @the-coding-beekeeper
    Posted almost 2 years ago

    Hi SonEfAdam!

    Congratulations for finishing this project! As you are new to HTML and CSS there are revealing some issues. Let me offer you some suggestions to improve the code:

    Give your body a width:

    body {
        width: 100vw;
    

    Size your grid-container correctly (overflow: hidden should be needless):

    .block {
    width: 42%;
    grid-template-columns: 50% 50%;
    /* overflow:hidden; */
    

    Give your image a width instead of a height and set it`s display to block, so that it fits into the grid-container:

    .dp-img {
    /* height: 600px; */
    width: 100%;
    display: block;
    }
    

    Then reduce the font-sizes and delete all the hard-coded px-margins. Replace the margins where needed with relative values like rem or em.

    in your html the button could be coded easier like following:

    <button class="button">
        <img src="./images/icon-cart.svg">Add to Cart
    </button>
    

    The .price element could be solved easier as following:

    .price {
        display: flex;
        align-items: center;
        /* height: 100px; */
    }
    
    

    These suggestions will not lead to a perfect solution, it is only intended to give you some food for thought.

    Happy coding and greetings from the-coding-beekeeper.

    Marked as helpful
  • P
    Azzumar•340
    @Azzumarithm
    Posted almost 2 years ago

    apply display : block onto the product image element to solve the 2nd problem.

    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

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub