Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 20 days ago

Responsive using picture/media query

Nhan Phan•50
@niophan
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 proud of figuring out how to use different images with picture element, and how to achieve border-radius when the view is divided into 2 parts( picture and text box) Besides, it is great to review somewhat sass, which i havenot touched for long.

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

I found it somewhat not similar to the original design, due to the difference of icon selection.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Rebecca Padgett•2,100
    @bccpadge
    Posted 20 days ago

    Hi Nhan Phan. Congratulations on completing this challenge!!!🎉

    HTML 📃:

    • Refactor index.html to incorporate HTML semantic tags.
    • Wrap Gabrielle Essence Eau De Parfum in <h1>.
    • Use <del> for the original price to apply an automatic strikethrough.
    • For the price section add more context for screen readers by deferentially the prices
     <div>
      <p class="product-price">
         <span class="visually-hidden">Current Price:</span>
          $149.99
      </p>
       <p class="product-original-price">
          <span class="visually-hidden">Orginial Price:</span>
          <del>$169.99</del>
       </p>
     </div>
    
    • The visually-hidden CSS class hides the text visually on the website but accessed by screen readers
    /* sometimes referred to as .sr-only */
    .visually-hidden:not(:focus):not(:active):not(:focus-within) {
      clip-path: inset(50%);
      height: 1px;
      overflow: hidden;
      position: absolute;
      white-space: nowrap; 
      width: 1px;
    }
    
    • Implement hover state for the button and cursor: pointer for better interactivity and make sure it focusable and usable by keyboard.

    Here is my solution to this challenge: Product Preview card component

    I hope you find this useful and don't hesitate to reach out if you have any questions.

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.

Oops! 😬

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

Log in with GitHub