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

Responsive product review card component page with HTML and CSS

Osiel Hernández•190
@xXOsielXx
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?

This time I was working with hsl. When I try to get dark the add-to-cart button I had to change the parameters of hsl function like this:

:root {
	--dark-cyan: hsl(158, 36%, 37%);
}

.add-to-cart {
	background-color: var(--dark-cyan);
}

.add-to-cart:hover {
	background-color: hsl(158, 36%, 27%);
}

From now on I will be using this CSS function more often.

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

I had problems making the card image responsive, because I didn't use javascript in this project. So, trying and trying I code of this way:


    

.banner.mobile {
	display: inline-block;
	border-radius: 8px 8px 0 0;
}

.banner.desktop {
	display: none;
}

@media only screen and (min-width: 600px) {
	.banner.mobile {
		display: none;
	}

	.banner.desktop {
		display: inline-block;
		width: 50%;
		height: auto;
		border-radius: 8px 0 0 8px;
	}
}

There may be other better ways to code it, but at the moment this is my solution.

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

If you know a better way of do it, you can tell me. I will really appreciate it.

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

  • Koda👹•3,830
    @kodan96
    Posted about 1 year ago

    hi there! 🙌

    There's no need to toggle images like this. You can use the <picture> element for this:

    <picture>
      
      <source media="(max-width: 600px)" srcset="small.jpg">
    </picture>
    

    (just include another source tag with a different image )

    or you can switch the image content within @media queries

    @media screen and (min-width: 45rem) {
    .your-img_classname: {
      content: url(your-img-path)
    }
    }
    

    Hope this was helpful🙏

    Good luck and happy coding! 💪

    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