Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted almost 3 years ago

Responsive Product Preview Card

EJ•100
@ejionaut
A solution to the Product preview card component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


There were quite a few things I struggled with and one of them is the responsiveness of the website. I am not sure if I did the sizing right.

I would love some feedback on the work, as I am a beginner :)

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Oshu•760
    @oshudev
    Posted almost 3 years ago

    Hi EJ 👋. You've done well on your first challenge. About responsiveness, there is a trick that I always use. Do max-width: (whatever the size you want) then width: 100%. In this way, when the view width is less than the set max-width, it will naturally scale to whatever the size of the parent element is. Then consider using the main tag and wrapping the card for accessibility. It goes like this:

    <body>
     <main>
      <section class="Main-Display"></section>
      <div class="attribution"></div>
    </main>
    </body>
    

    Another thing is that you can't use z-index if there is no position property. And also, align-self and justify-self can't be used if you're not using display: grid. You should use align-items and justify-content on flex-box. Also, check the report for other issues as well.

    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 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