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

NFT Card using HTML and CSS

Ly Dinh Minh Man•260
@winprn
A solution to the NFT preview card component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


I would really appreciate your feedback and also guidance on how to make the site works better. Thanks in advance!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Kehinde•680
    @jonathan401
    Posted almost 3 years ago

    Hey there @winprn 👋🏽 congrats on completing this challenge 🎉🎉🎉. You did really well. Just a few things from me 😄.

    1. This isn't really a feedback but you should consider checking out the report on your solution. This has help me a lot 💪🏿. For example, you should wrap your whole card in main element.
    2. You could consider changing the .card-title which is currently a p element to an h1 element. This is because it is required that every page contains at least one h1 element for easily navigation of the page by other users who may have some disabilities.
    3. When I checked out your solution on my mobile phone, the card was stretched over the screen. To fix this, instead of adding a definite to the card, you could consider giving a max-width style rule to the card instead of a width to the card. This will make sure that the card easily 'contracts' on mobile screens and then on larger screens you remove this max-width and adding a definite width of 37.5rem (which you defined in your CSS for larger screens). That is all from me 😄. Once again nice work 👏🏾. Happy Coding 🎉
    Marked as helpful
  • Ayomide Gidigbi•100
    @Draysongz
    Posted almost 3 years ago

    Its a great design, but add cursor pointer style to the main nft image

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

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub