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

Basic NFT card using HTML and CSS

Joshua•30
@zepolj1126
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

  • Jayme•50
    @jaymew88
    Posted about 3 years ago

    Hey!

    Great job on your first challenge! The project looks great.

    A couple of things that were already mentioned in your feedback, that I noticed as well, deleting any unnecessary comments and using CSS variables for colors and fonts. On additional thing I would like to add is the Document should have one main HTML element, contain the component in <main>.

    Can't wait to see more!

    Marked as helpful
  • Eric Salvi•1,350
    @ericsalvi
    Posted about 3 years ago

    Hey!

    I love the solution you did for the hover effect on the image and revealing the eye icon. When I did this, I struggled a bit but yours is a bit more simplified. Great job with your first submission.

    A few things to keep an eye out for would be after you submit your solution, check out the report that gets generated to check for errors and accessibility issues.

    View Report Here

    A tool you could use in Chrome Dev Tools before you submit is AxeDevTools (extension download).

    Another thing I would suggest doing is to remove any unneeded comments from your HTML and CSS and make sure to remove any CSS that is not needed (ie. .attribution).

    One thing you could try to start using is CSS Variables for things such as colors. It makes it so much easier to code, I found.

    Great job again, and I look forward to seeing more submissions from you in the future.

    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