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

NFT preview card with HTML & Css

accessibility
kounik•300
@Valhalla-2
A solution to the NFT preview card component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


  1. I find it a little difficult building the image hover effect
  2. what is the best method of doing the image overlay effect ?
Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Lucas 👾•104,160
    @correlucas
    Posted almost 3 years ago

    👾Hello @Valhalla-2, Congratulations on completing this challenge!

    Here’s some tips to improve your component design:

    1.I saw that you’ve used id to give the styling for your component, its not a good idea because id its a too much specific selector used for forms and Javascript code. Instead, use class for styling and let the id for much specific stuff.

    It is not advisable to use IDs as CSS selectors because if another element in the page uses the same/similar style, you would have to write the same CSS again. Even if you don't have more than one element with that style right now, it might come later.

    2.You can create a media query to save space in the pricing section to make each information in a different row. Here’s the code for this media query.

    @media (max-width: 350px) {
    .wallet {
        display: flex;
        justify-content: space-between;
        font-size: 18px;
        flex-direction: column;
        align-items: center;
    }
    }
    

    ✌️ I hope this helps you and happy coding!

    Marked as helpful
  • Vanza Setia•27,715
    @vanzasetia
    Posted almost 3 years ago

    Hi there! 👋

    For the image hover effect, I would recommend creating it with pure CSS, pseudo-element and background properties.

    Before start creating the overlay, we need to get the HTML right first.

    • The Equilibrium image needs to be wrapped by an anchor tag. It has interactivity so it should be wrapped by interactive element.
    • The alternative text for the image should be the text content for the link. When I was doing the challenge, I set the value for the href to the image. The purpose of the link was to allow the users to preview the image. So, the alternative text is "Preview Equilibrium".

    Then for the styling,

    • Create one pseudo-element from the anchor tag.
    • Then make the pseudo-element fill the entire image.
    • After that, when the anchor tag gets hovered (a:hover::before), you can add the cyan overlay and the eye icon using background properties.
    • Lastly, for the cyan color, I recommend using the hsla color format. This way, you can reduce the alpha (opacity) of the cyan color.

    For your inspiration, you can take a look at my solution.

    Hope this helps! 🙂

    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

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