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

Product preview card component

👾 Ekaterine Mitagvaria 👾•7,860
@catherineisonline
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, Frontend Mentor community! This is my solution to the Product preview card component.

I appreciate all the feedback you left that helped me to improve this project. Due to the fact that I published this project very long ago, I am no longer updating it and changing its status to Public Archive on my Github.

You are free to download or use the code for reference in your projects, but I no longer update it or accept any feedback.

Thank you

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • ApplePieGiraffe•30,525
    @ApplePieGiraffe
    Posted almost 3 years ago

    Hey there, Catherine Is Online! 👋

    Great job on this challenge! 👏 Your solution looks good and responds well! 🙌

    One thing I'd suggest is to probably not set the font-size of the text in the body in px because we typically want to users to be able to change the size of all text on the site by the changing the root font-size of the document. In other words, setting font-size in em or rem wherever possible would be the better way to go in order to make your solution as accessible as possible. 😉

    Hope that helps. 😊

    Keep coding (and happy coding, too)! 😁

    Marked as helpful
  • faizan•2,420
    @afaiz-space
    Posted almost 3 years ago

    Hey @catherineisonline, remove height: 450px; from main element.

    Marked as helpful
  • lilKriT•400
    @lilKriT
    Posted almost 3 years ago

    Very cool and clean. It almost looks like the design is a screenshot of your implementation.

    Marked as helpful
  • DkP-Consult•60
    @DkP-Consult
    Posted almost 3 years ago

    Well good job ! Just may be use bold propertie for promo price :) Friendly, DkP

    Marked as helpful
  • Renan Tiscoski•1,240
    @DonUggioni
    Posted almost 3 years ago

    Looks spot on! Great job 👍

    Marked as helpful
  • MazzCode•120
    @MazzGuille
    Posted almost 3 years ago

    Hi, I think the only suggestion I can give you is to set the font size on HTML or body to 62.5%, this makes 1rem = 10px, that way you can use rem units to set specific font sizes on different elements. I.E., by setting font size to 62.5%, if I wanted a <p> tag to be 16px, I would set it like this:

    html { font-size: 62.5%;
    }

    .my-p-tag{ font-size: 1.6rem; }

    This also helps because you can use rem units for padding, margins or any other measurement you need

    Hope it's helpful for you!

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.

Frontend Mentor for Teams

Frontend Mentor for Teams helps companies and schools onboard and train developers through project-based learning. Our industry-standard projects give developers hands-on experience tackling real coding problems, helping them master their craft.

If you work in a company or are a student in a coding school, feel free to share Frontend Mentor for Teams with your manager or instructor, as they may use it to help with your coding education.

Learn more

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

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