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

CardProductResponsive

Farid_Danilo•140
@FaridDanilo
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?

Being able to complete this new challenge, as always, makes me feel proud, but I know that it can still be done better and I can show a better result.

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

One of the main challenges I encountered was adjusting the styles to fit the design for mobile devices. It was quite challenging, and finding a way to make it look as it should meant I had to resort to several guides to get the design I wanted.

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

I would like help accommodating and improving further the ability to create fluid pages that adapt well to devices (especially mobile devices) without losing that sophisticated and attractive design that draws attention.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Harsh Kumar•3,850
    @thisisharsh7
    Posted about 2 months ago

    ✅ Great job on fonts, color palette, and layout – looks clean and professional.

    • 📱 Mobile Issue: h1 gets cut off on small screens due to fixed width. 💡 Fix: Remove or adjust width: 15ch in mobile, use:
        h1 {
            width: 100%;
            font-size: 2.2rem;
        }
    
    • 🧠 Tip: Avoid fixed widths (like ch) for text; use max-width or let it wrap naturally.

    • 📌 Suggestion: Replace absolute centering with Flexbox for better responsiveness:

        body {
            display: flex;
            justify-content: center;
            align-items: center;
            min-height: 100vh;
        }
    

    Keep it up! Solid work – just refine mobile handling and layout flexibility.

    Marked as helpful
  • Marzia Jalili•8,230
    @MarziaJalili
    Posted about 2 months ago

    You've nailed this, man! 🎉

    🌟 A tiny little suggesteenoo?

    ✅ If the old price is meant to be shown as "crossed out" or "discounted from", use the <del> element.

    ✅ Screen readers may announce it as "deleted" or "no longer valid", helping users understand that it's an old price.

    ✅ Here's the updated code:

    <div class="price-product">$149.99 <del class="discount">$169.99</del></div>
    

    😎😎😎

    Marked as helpful

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