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

Product preview Card Component

theritikyadav11•40
@theritikyadav11
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?

The desingning of responsiveness make me proud. For the second time I go with mobile first approach.

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

I developed desktop view easily but when I am developing the mobile I am facing some problem and by the help of some documentation I resolve this challenges.

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

Making the project responsiveness because making the exact design is easy but when it comes to responsiveness it is some challenging but now I understand the concept we need to follow mobile first approach.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Joshtemi0•200
    @Joshtemi0
    Posted 3 months ago

    Good job.

    But I was expecting to hover on the button and the cursor should change to pointer.

    And will advise to use external link for your CSS.

  • Shah Faisal•460
    @Shah-Faisal-cloud
    Posted 3 months ago

    Great job.

    To enhance the interactivity, you could add a subtle background color change on hover to visually indicate that the button is clickable. Also, setting the cursor to pointer on hover would reinforce this feeling to users.

    Additionally, to keep the code organized and maintainable, it’s a good idea to separate the CSS from the HTML by creating an external CSS file. This approach keeps your HTML clean and makes future styling changes much easier.

    Here’s a quick example of what you could do:

    /* styles.css */
    button {
      background-color: #4CAF50;
      border: none;
      color: white;
      padding: 10px 20px;
      font-size: 16px;
      cursor: pointer; /* Makes cursor a pointer */
      transition: background-color 0.3s ease;
    }
    
    button:hover {
      background-color: #45a049; /* Slightly different bg on hover */
    }
    

    And then link this CSS file in your HTML:

    <link rel="stylesheet" href="styles.css" />
    

    Hope this will be 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