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

Product preview card component using HTML & CSS

Yahir_AM•370
@Yahir-am
A solution to the Product preview card component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Hi everyone, a feedback will be appreciated :D

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    Treasure Kabareebe•290
    @trekab
    Posted almost 3 years ago

    Nicely done, @Yahir-am! I like your use of CSS variables. They make your CSS readable and more maintainable. However, here are some suggestions to make your page look even better:

    • The mobile version appears to have some excess bottom white spacing after the button. Clearing this would make your page look more like the design spec.
    • It would also be great to provide a fallback font whenever you specify a font family in your CSS. e.g. font-family: "Montserrat", sans-serif; would imply that sans-serif is the fallback font. I find the introduction of this article(CSS Fallback Fonts) insightful about fallback fonts.
    • Finally, writing mobile-first CSS is a nice practice to follow when building responsive web pages. Here is a great article for more insight.

    I hope you find this feedback beneficial

    Happy coding!

    Marked as helpful
  • Account deletedPosted almost 3 years ago

    Hi Yahir,

    Great solution! This is looking really good.

    The only thing I would suggest is limiting the height on mobile/smaller screens - The width resizes nicely, however the height adjusts to the screen's size without there being any content, so you end up with a lot of empty white space below the button.

    Other than that, this looks spot on! Well done 😊

    Marked as helpful
  • Akanni Feyisara•110
    @Feyisara2306
    Posted almost 3 years ago

    Well done! You have no issue at all. I just completed the same project but it isn't as perfect as yours. I've got some questions if you don't mind, how did you centralize the elements on the page? and also, the display I get on my browser when coding isn't the same as the one that shows with the live site url, I want to know what I'm doing wrong, Thanks.

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

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub