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

NFT preview

Thomas Hertog•885
@thomashertog
A solution to the NFT preview card component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)
Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Grace•32,130
    @grace-snow
    Posted over 3 years ago

    Hello

    This would be much better if you used pseudo elements for the hover effect. It's questionable whether it's even valid html to have divs inside anchor tags.

    I suggest using hsla for the background color of the pseudo and making the eye a background image on the pseudo.

    Alternatively, you could use 2 pseudo elements and z-index to stack them, so the turquoise layer with the lower opacity sits 'underneath' the pseudo with the eye image.

    You definitely need to add display: block; to the image whatever approach you take. Your overlays are not sitting flush over the image at the moment as it is an inline-block element by default.

    The other essential change is to improve the label of that link on the image. At the moment the only link content is the alt of the image, which is poorly written. You should never write "image" or "photo" etc in alt text as it is already an image element. If that is the only link content, it needs to say what the image actually does. OR you need an aria-label or sr-only text in that link to say where the anchor tag will take you to.

    Looking at the stats, you've not used meaningful elements there. It's important to always use meaningful elements for text, never just a div or span. It would be improved if you made stats an unordered list, and value expiry into list items.

    I don't think it makes sense using a footer element like you have at the moment. It would kind of make sense if this was an article, not a section. But even then, although it's considered OK, it's really annoying to screenreader users when there are loads of headers/footers on a page. Even in articles, it's not usually a nice experience for them. Heading structure is the most important thing for page structure / semantics and you've already nailed that fine!

    Good job on this overall. I hope the suggestions are helpful

    Marked as helpful
  • Remus D. Buhaianu•3,125
    @remusbuhaianu
    Posted over 3 years ago

    Congrats on completing the challenge, Thomas!

    You did a great job on your HTML and CSS code. I don't have too many comments to make given how well you did the project, but I have a little suggestion for another approach to the overlay effect: instead of adding those HTML elements, you can use the ::after and ::before CSS pseudo-elements to create the effect.

    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.

Frontend Mentor for Teams

Frontend Mentor for Teams helps companies and schools onboard and train developers through project-based learning. Our industry-standard projects give developers hands-on experience tackling real coding problems, helping them master their craft.

If you work in a company or are a student in a coding school, feel free to share Frontend Mentor for Teams with your manager or instructor, as they may use it to help with your coding education.

Learn more

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