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

NFT preview card component (mobile-first workflow)

Abdeljalil wahib•80
@Ajwahib95
A solution to the NFT preview card component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


this challenge was relatively easy until I had to code the active states, the hover effect on the image was very hard to figure out, I searched for an entire day on how to change the color of a jpg image but nothing seemed to give the expected results. so I tried to find my own solution, which I did.

basically what I ended up doing was I lowered the opacity both on the image itself and the background color ,after that worked I had another problem where I would hover on the view-icon and the hover effect would break, so to solve that I had to make the view-icon the actual trigger for the hover effect, and for that to work I had to give the view-icon the same width as the NFT image, and to prevent the icon from stretching to fit that width I used "object-fit: scale-down".

.NFT:hover {
    opacity: 0.5; 
  }
  .img-div:hover .view-icon {
    visibility: visible;
    background-color: hsl(178, 100%, 50%, 0.5);
    border-radius: 10px;
  }

 .view-icon{
   position: absolute;
   visibility: hidden;
   z-index: 9999;
   width: 281px;
   object-fit: scale-down;
  }

honestly although it works, I'm not so sure about the approach I took to solve this challenges, I would appreciate some feedback on that.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on Abdeljalil wahib's 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.