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

NFT preview challenge

Kariman Medhat•170
@KarimanMedhat
A solution to the NFT preview card component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


In the active mood, I couldn't do the overlay with the icon inactive mood, I searched for a way but it didn't work. Does anyone have a way that will work?

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Acme Gamers•295
    @AcmeGamers
    Posted about 3 years ago

    Hey there 👋,

    Congratulations on nearly completing the challenge 🥳! You did great on centring the whole <main> tag using transform 😊.

    I would recommend changing the paragraph color to a bit lighter tone so people with eye issues can read it with ease. As far for the issue of hovering on the image that you were having, we use pseudo elements for that, things like ::before, ::after, :first-child, etc. However, pseudo elements does not work on <img> elements, so to cover that issue, we use the <div> tag.

    Solution (Spoiler Alert)

    HTML

    • Change your <img class='main-img'> element to <div class='main-img'> element
    • Yup, that's all for HTML! :D

    CSS

    Add a background image to the div

    .main-img {
        background: url("images/image-equilibrium.jpg");
        background-size: contain;
    
        min-height: 268px;    
        width: inherit;   // Inherits the available width
    
        border-radius: 20px;
    }
    

    Let's add the pseudo :before state on the div element

    .main-img::before {
        content: "";       // This is important, it won't work without it
        display: block;
    
        height: inherit;   // Inherits the div height
        width: inherit;    // Inherits the div width
    
        background: red;
        opacity: 0.6
    }
    

    If you reach here, it means you may have got a complete red square on your NF T image. But the question is, we want it to appear when it hovers, so try doing some research on how to add hover on ::before, if you figure it out, congrats, you are moving at a fast pace! :DDD

    If it still confuses you, drop a reply and I will be here to explain it with an easier method 😊. Hope to see your future success and designs, until then, best of luck!

    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