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

productPreviewCard_figmaChallenge

P
Anjelica•160
@Anjie-MF
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 that I took the time to build the layout from scratch without immediately relying on AI, and that I figured out how to properly structure the responsive image component and the "Add to Cart" button (including hover states and icons). Looking back, I'd like to approach spacing (padding/margin) more systematically next time — maybe by setting up a layout grid earlier or adding temporary outlines/borders during development to catch inconsistencies faster.

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

Spacing was a big challenge — especially balancing margin, padding, and ensuring the image filled its container properly across screen sizes. At first, I thought I fixed the problem by adjusting the card width, but further testing revealed deeper issues. To solve it, I went back to basics: inspecting elements in dev tools, experimenting with flexbox vs. grid, reviewing my two-year-old code, and getting feedback from AI to spot mistakes I missed. It reinforced how important careful testing and debugging are, not just "visual fixes.

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

I'd love feedback on my layout structure — particularly if there are cleaner ways to handle spacing and alignment earlier in the project without needing multiple rounds of tweaking. I'd also appreciate advice on best practices for structuring media queries and scaling a layout for larger screen sizes in a more maintainable way.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Varun Tyagi•150
    @vitviki
    Posted over 1 year ago

    Hey,

    1. To add the cart icon inside the button use img tag inside button tag like so:

           <button class="cart_btn">
              <img src="./images/icon-cart.svg" alt="cart">
             Add to Cart
            </button>
      
    2. Instructions to add screenshot in README can be found in README-template.md. For some reason I'm unable to write the command here. It's not showing up in the preview.

    Hope this helps.

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