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

Responsive page - Product preview card component

Jose Miguel Galdamez Madrid•80
@Josmiga
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?

Im very proud about make my first responsive page, a mean, you can see thiis page perfectly in your mobile device and your desktop browser.

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

In the last projects I always set a default width on my main , this time I use a scalable width and that makes me do a little research about responsive pages because my page was going crazy with the layouts.

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

I want all the advices posibles about responsive images.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Yash Bhatt•280
    @Y-ashbhatt
    Posted about 1 year ago

    Hello!

    Your solution loooks pretty good.

    But I noticed there was tiny mistake in rounding the corners in the Image. In the desktop design it still follows the mobile design format.

    For giving corners different border radius try this article Border Radius. This explains how to separately round each corner in a simple way.

    I hope you find it helpful.

    Marked as helpful
  • P
    Daniel 🛸•44,830
    @danielmrz-dev
    Posted about 1 year ago

    Hey there! 🙋🏽‍♂️

    Congrats on finishing the challenge! ✅

    Your project looks awesome!

    Here's a tip that might interest you:

    📌 When you have different versions of the same image, consider using the <picture> tag instead of using the image as background.

    This will help ensure the correct image loads on the user's device, saving bandwidth and boosting performance.

    Example:

    <picture>
        <source media="(min-width: 768px)" srcset="{desktop image path here}">
        <img src="{mobile image path here}" alt="{alternative text here}">
    </picture>
    

    Hope you find this useful!

    Great job overall!

    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

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