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

Product preview card using HTML CSS Flex Box Model Media Query

P
librart•150
@librart
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 learned how to use the root: {} selector and media query, but I still need to learn more about media query for responsive web.

What challenges did you encounter, and how did you overcome them?

I still need to learn more about media query for responsive web.

What specific areas of your project would you like help with?

I think I would love to get feedback for all of my code from HTML structure to CSS styles, especially the responsive design.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    Kamran Kiani•2,780
    @kaamiik
    Posted 5 months ago

    A few notes:

    1. The word perfume on your page appears to be used as a tag, so it would be better to use a p tag instead of an h2 tag.

    1. Try tackling this challenge using the grid system as well. It’s much easier and the results will likely be better. Plus, it's a great practice exercise.

    1. The Add to cart element should be a button in a larger context, as you don't want to change the webpage but rather perform an action.

    1. Regarding your button's styling, if you narrow your page, the text starts to wrap due to the horizontal padding. This can be fixed by using only vertical padding, like 15px 0, and adding justify-content: center;.
    Marked as helpful
  • yuriinyk•150
    @yuriinyk
    Posted 6 months ago
    1. Semantic HTML: Good use of semantic tags like <main>, <article>, and <picture>. Consider adding aria-label for better accessibility. 2. Accessibility: Improve the :focus state visibility and add descriptive alt text for images. 3. Responsive Layout: Looks good on mobile and desktop. Test on tablets and refine typography scaling with clamp(). 4. Code Structure: Well-organized CSS with variables. Add comments for better readability and separate reusable styles from layout-specific ones. 5. Design Match: Faithful to typical product card designs. Double-check spacing and padding for pixel-perfect accuracy.

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