Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted over 1 year ago

Responsive card product, using flex and grid.

Nantue Polchevski•170
@Nantue
A solution to the Product preview card component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)
Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • juss-10•40
    @juss-10
    Posted over 1 year ago

    Hello!

    Congrats on finishing the challenge! Visually the component looks very close to the design, but there are a number of issues in the code.

    Here are some problems I noticed:

    Height and Grid

    Using 100% in body { grid-template-rows: 100% 1fr } occupies 100% of the height set by body { height: 100vh } for the first grid row, which does not leave any additional space for 1fr in the second grid row. This is causing the text in <div class="attribution"> to overlap with the product card.

    • You can change body { height: 100vh } to body { min-height: 100vh } as well as change body { grid-template-rows: 100% 1fr } to body { grid-template-rows: 100% auto } or body { grid-template-rows: 1fr auto }.

    • Setting body { min-height: 100vh } can have some issues on mobile, but there are other ways of approaching setting a height for body. I recommend you look more into this.

    Use <picture>

    1. I would not recommend using two separate img elements and hiding one or the other when needed. Instead, you can use the <picture> and <source> elements along with the img element and an inline media query with the media HTML attribute on the <source> elements to specify which image to use when the width of the viewport is at that size:
    <picture>
    	<source media="(min-width: 60rem)" srcset="images/large-image.png">
    	<source media="(min-width: 40rem)" srcset="images/medium-image.png">
    	<img src="images/small-image" alt="Description">
    </picture>
    

    Capitalize text in CSS

    Instead of capitalizing text in the HTML, use CSS to do this.

    selector {
    	text-transform: uppercase;
    }
    

    Price elements

    The price does not need to be a heading and the structure can be simplified a bit. There are few other adjustments here that you can make. - The visually-hidden class will visually hide Old price: for sighted users and allow users with screen readers to hear this text. You can find out more about using a visually-hidden class online.

    <p class="price">
    	<span>$149.99</span>
    	<s><span class="visually-hidden">Old price: </span>$169.99</s>
    </p>
    

    Buttons

    I'm not sure why you used a div element for the button, but that's not recommended. That is not a button. Use a <button> element for "actions" and use <a> for links. You sometimes may have links (<a>) that look like buttons, but still only use <button> for actions and <a> for links.

    Decorative images and icons

    The shopping cart icon in the button is decorative, so it doesn't need to include a value for alt text.

    Product Card Container

    Personally, I would not have used <main> as the container for the product card. I would use its own container. This might be <article>, possibly <section>, or just <div>.

    I hope this helps!

  • Nantue Polchevski•170
    @Nantue
    Posted over 1 year ago

    Almost perfect

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