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

Responsive NFT preview card component Using HTML5 and CSS3

Michael Johnson•100
@michaeljohnson-mj
A solution to the NFT preview card component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Hello Developers,

I have completed the NFT preview card component. I would love to receive some feedback on the hover state of the card image.

Cheers!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Raymart Pamplona•16,040
    @pikapikamart
    Posted over 3 years ago

    Hey, really nice work on this one. Layout in general looks really great.

    Some suggestions on the site would be:

    • Avoid using height: 100vh on a large container like the body as this makes the element's height capped based on the viewport/screen's height. Instead use min-height: 100vh so that the element will expand if it needs to.
    • But doing that makes the layout not centered anymore. So add an extra :
    align-items: center;
    display: flex;
    

    On the body tag.

    • Since you are treating the image as an interactive, since there is a hover with something like a preview state right, it would be great to use button in here. It would wrap the whole img so that user can properly focus on it and could toggle the preview if they want with just using keyboard.
    • Sine the Equilibrium text is an interactive element, supposing it would be a page-link where user can view the full information about the nft? What is nft :>> It would be great to use :
    <h1>
      <a href="/images/nft">Equilibrium </a>  # or just use href="#" for now
    </h1>
    
    • But to be honest, I wouldn't use h1 on the nft name in here, the h1 would be a screen-reader only heading inside the main. Since by looking at this component, on a real site, there would be numbers of different nft? Images in here so using the h1 as a general text would be lot better and using just h2 on the nft? Title.
    • The 0.041ETH should be inside a p tag. Remember that you don't wrap a text directly with a div element, always use a more suitable tag for texts.
    • The clock image is just a decoration on the site. Decorative images should be hidden for screen-reader at all times by using alt="" and aria-hidden="true" to the img tag or only aria-hidden="true" if the image is using svg.
    • Only use descriptive alt on images that are meaningful and adds content to the site otherwise hide the image for screen-reader users.
    • Again, use p tag on the 3-days-left.
    • Person's image should be using the person's name as the alt attribute since it is already visible, `alt="Jules Wyvern".
    • The person's name as well is treated as interactive component so use a interactive element on it like a a tag if this would like navigate a user on a different site.

    Aside from those, great job again on this one.

    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