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

NFT Preview

Diana Jordan•20
@dee-jordan
A solution to the NFT preview card component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Completed this NFT Preview challenge. I always seem to have issues with hovering and span functions. If anyone has any tips and resources of the thought process or good practice tips, I would like to be able to determine how to use these functions on my own.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • imad•3,330
    @imadvv
    Posted over 1 year ago

    Greeting Diana Jordan! Congratulations for completing your challenge!, 👏👏👏.

    they is a lot of ways to archive this overly effect, this is good resource from w3school, and also this blog post has some good information, but I did some changes to your code to make it function,

    html

        <div class="images">
          <img src="images/image-equilibrium.jpg" alt="equilibrium" class="image-first">
        </div>
    
    

    css

    
    main .images{
        position: relative;
        background-color: rgb(139, 213, 218);
        border-radius: 10px;
        z-index: 1;
        overflow: hidden;
    }
    
    .image-first{
        max-width: 100%;
        transition: opacity 200ms ease-in-out;
    }
    .images::after{
      content: "";
      position: absolute;
      background-image: url("./images/icon-view.svg");
      background-position: center;
      background-repeat: no-repeat;
      width: 3rem;
      height: 3rem;
      top: 50%;
      left: 50%;
      transform: translate(-50%, -50%);
      z-index: 10;
      opacity: 0;
      visibility: hidden;
      transition: all 250ms ease-in-out;
    }
    
    .images:hover .image-first{
      opacity: .2;
    }
    .images:hover::after {
      opacity: 1;
      visibility: visible;
      scale: 1;
    }
    
    
    

    this implementation uses css pseudo-elements, I Hope this give you some hints or tricks after all good attempt, keep 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