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

responsive using media query

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

Solution retrospective


What did you find difficult while building the project? =css tires me the work was time consuming.

Which areas of your code are you unsure of? =i worked my ass off the best way i can on this website even as a newbie so there is no are I am unsure about.

Do you have any questions about best practices? =there must be some very basics and the challenges should be in a level format like level 1 qr-code level 2 card-review something like that and each clearing increases the level of the user interacting to frontend that will totally very good way i think from my perspective.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    visualdennis•8,375
    @visualdenniss
    Posted over 2 years ago

    Hey there,

    good job completing the challenge successfully. Your implementation looks great overall. One tip i'd have is that i noticed there is a little tiny white space below the image.You can get rid of that easily by:

    img { display: block }

    images are technically set to display: inline (like text) by default but behave like inline-block (meaning one can set width and height explicitly). You can see that text have usually some tiny white area below and above the letters. So this is where this behaviour comes from. By display: block, you can get rid of that.

    Hope this was helpful!

    Marked as helpful
  • Alexej Kunz•60
    @Orchi1904
    Posted over 2 years ago

    Hey @aaishver,

    I am very happy with your solution, it looks great. There are only three small things that make it better in my opinion:

    • It is great that you used a footer element for the attribution but the footer element should be inside the body element, because the footer is part of the website

    • Your solution looks even better if you center the card. This is possible if you add the following things to your body-selector in your CSS:

    body{
        padding-top: 8rem;
        background-color: hsl(30, 38%, 92%);
        margin: 0; /*Get rid of unnecessary margins*/
        padding: 0; /*Get rid of unnecessary padding*/
        height: 100vh; /*Body height is now full viewport height*/
        display: flex; 
        flex-direction: column; /*Use this so that the card and the footer are below each other and not next to each other*/
        justify-content: center; /*Center the card vertically*/
        align-items: center; /*Center the card horizontally*/
    }
    
    • <p> are not allowed as a child elements of <button>. You should rather use a <span> element inside the button like so:
    <button>
       <img src="images/icon-cart.svg" alt=""/>
       <span>Add to Cart</span>
    </button>
    

    I hope this was helpful for you. 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
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