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

Product-preview-card-component-main

Eleonora Stoyanova•70
@elistoyanova
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 are you most proud of, and what would you do differently next time?

I'm my second time making this project. It's been a while since the first try and since then I see improvement. Back then I needed to google some stuff in order to code them, but now I managed to fully make it by myself

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Onyinyechi Viola Obika•240
    @Obikaviola
    Posted 2 months ago

    Hi Elenora,

    Amazing work here 👏🏾👏🏾👏🏾

    You structured your code in a clean and precise way. I actually learned a few things from you. 😁

    I do have one suggestion though. It's concerning the images. It seems you put one in the HTML file and the other in CSS. It's not entirely wrong to put images in CSS but putting images in CSS is meant for images that are just there for decorative purpose and have no impact on the SEO.

    Placing images in HTML allows it to be accessible for indexing by not crawlers which adds to the SEO. In this case, being a product preview of a perfume, the SEO impact of the image is important as such the images ought to be placed in the HTML.

    If you're worried about how to place two images that changes depending on screen size, use the picture element. Here are helpful articles to help you understand it better:

    -mdn web doc -[W3school picture element] (https://www.w3schools.com/html/html_images_picture.asp)

    Great work overall 👍🏾👍🏾👍🏾

  • MhdSinanC•110
    @MhdSinanC
    Posted 2 months ago

    Hello there,

    Looks so identical, But your mobile design is not yet responsive. The image is shrinking. It need to be on the top in mobiles.

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