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

NFT-Preview-Card-Component

Aniket Saini•30
@AniketSaini98
A solution to the NFT preview card component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Please feel free to give your review on this all reviews are welcome.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

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

    Hello there, Aniket Saini! 👋

    Congratulations on finishing this challenge! 🎉

    Here are some suggestions for improvements.

    • Currently all the elements that have interactivity are not interactive elements. For example, the NFT image should be wrapped by an anchor tag, the "Equilibrium #3429" also should be wrapped by an anchor tag (make the anchor tag as the child element of the h2).
    • Always wrap text content with a meaningful element like a paragraph element whenever possible.
    • Alternative text should not be hyphenated (like code). Also, it should not be containing the word "image" or "icon" because the semantic meaning of the img element is already enough to make the screenreaders pronounce them as an image.

    Hope this helps! 🙂

    Marked as helpful
  • Azhar•600
    @azhar1038
    Posted almost 3 years ago

    Hi Aniket, nicely done!

    I noticed that you have used @media screen and (max-width: 1440px) to handle the sizing, so in larger screen > 1440px, your card is taking whole width and breaking the design. You should not use such media query. It is present in design document to tell that frontendmentor uses that to generate images.

    Another problem is your eye image that appears on hover, it is not responsive, so in smaller screen it does not cover whole picture. You can wrap your images in div and position it absolutely w.r.t that inner div instead of main container.

    Hope it 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