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

Responsive Product Card Design

Dheeraj Kumar Yadav•30
@Dheeraj-Yadav8178
A solution to the Product preview card component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Hello guys👋, this is my second project please watch it and give your feedback how is it. Thank You😊

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • S MD suleman•3,510
    @sulemaan7070
    Posted over 2 years ago

    A few things you can add to make it perfect.

    1. font family and font-weight to the h1.
    2. font family of the pricing section.
    3. you can give the image a max-width of 100%(so that it can be fit to the div).
    4. finally the text-container should be limited to a certain width on the mobile view
    5. you can change the whole body color instead of wrapper
    Marked as helpful
  • Piyush jain•220
    @PiyushJain01
    Posted over 2 years ago

    Hi 👋 You can give background :#ffe6ff; to body instead of .wrapper because in mobile view some area at bottom side is not covered by the color also the wrapper is not aligned vertically center (in small screens). You can add the below code to fix these problems.

    body {
        height: 100vh;
        display: flex;
        background: #ffe6ff;
        flex-direction: column;
        justify-content: center;
    }
    

    I hope this will help you. Rest all is perfect. Happy Coding :)

    Marked as helpful
  • Can•235
    @escarcan
    Posted over 2 years ago

    Looks good! just remember to add the "alt" attribute to your img tags to improve accesibility and wrap your code with a main tag to fix your reports.

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

Oops! 😬

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

Log in with GitHub