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

Responsive Product Card Using Only HTML and CSS

Nafis Sazzad Niloy•190
@methane-js
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 am proud because I have successfully designed this product card with stylish fonts, letter spacing and line height.

I want to continue developing my skills like this way

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

I encountered a challenge which was to make the website responsive with different image.

But I used the background property of CSS and overcome the challenge easily.

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

In my every projects, I see that my website view on my computer and on the live hosting platform doesn't look same.

If you know why this is happening, please tell me.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Marzia Jalili•8,410
    @MarziaJalili
    Posted 5 months ago

    Nice work!

    Some sort of suggestionfor you to consider in your next projects

    • Instead of using the div element to wrapp the img inside, you could use the picture element.

    The picture element is very handy when it comes to multiple images for different screen sizes. It gives you the ability to set different media attributes which can declare the screen size for each source element nested inside.

    You can take the code below as an example:

    <picture>
      <source 
        srcset="(path of mobile image)"  media="(max-width: 30em)"
       />
      <source 
        srcset="(path of desktop image)"  media="(min-width: 31em)"
      />
      <img src="(path of the image)" alt="image"/>
    </picture>
    

    The src attribute in the img will be the fallback source of the image if the other sources are not found.

    • Also, Could you provide me with some further information about the issue with hosting, like what exactly the problem is?

    I will surely help you out if I find the solution.

    😁😁😁

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