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

Product preview component using html and css

Ravindra Suresh Kadam•80
@socoolRK
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 have completed another challenge from a front-end mentor and I am struggling to make it responsive, can anyone guide me to make it responsive. I will appreciate the valuable feedback.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Fernanda•180
    @ferlagher
    Posted almost 3 years ago

    Hi, Ravindra!

    There are many ways to make a design responsive. You can use media querys, relative units, flexbox, grid, or a combination of all of them.

    Here are some resources:

    • Media querys
    • CSS Units
    • Flexbox
    • Grid
  • Lucas 👾•104,160
    @correlucas
    Posted almost 3 years ago

    Hello Ravindra, congratulations for having finished another challenge!

    I'm with your solution website open and the component seems great. You need only to fix some minor issues and apply a media query to display the component vertically as the mobile version.

    I'll give your some tips:

    1.Align your card component to the screen center using flexbox and height:100vh;. Note that the height:100vh will allow you to have the body displaying 100% of the viewport making easier to align, see the code below:

    body { display: flex; height: 100vh; align-items: center; justify-content: center; }

    2.Add a margin around the container to create a free space around the card and dont let the card touch the screen limit in smaller screens.

    body {margin: 20px;}

    3.Add a media query to change the card flow changing it to display one column and the content vertically. Not that a media query is a tool that allow your to apply changes to a certain element in a certain breaking point, in my following example the breaking point is width 700px. Code below:

    @media (max-width: 700px) { .container {display: flex;flex-direction: column; }}

    See the documentation about Media Query here: https://www.w3schools.com/css/css_rwd_mediaqueries.asp

    4.To change the text-decoration and add a line over the "discount price" you can use this property in the price element: text-decoration: line-through;

    Ravindra I think that applying these changes your card will be fixed. Feel free to ask me any question and I hope it helps you. Happy coding.

  • Rafi Mahmud Rizvi•130
    @RafiiMahmudRiizvii
    Posted almost 3 years ago

    Hi Ravindra, i notice that the font-family of "$149.99" is not match with original design. If you change the font-family then your design look more beautiful.

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

Oops! 😬

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

Log in with GitHub