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

NFT Card Preview (Desktop Version)

Ali Mousavi Nizhad•270
@mnizhadali-afg
A solution to the NFT preview card component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Just updated the final version :)

Happy coding to everyone.

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • Travolgi 🍕•31,280
    @denielden
    Posted over 3 years ago

    Hi Ali, great work and congrats on completing the challenge!

    • For center the card give height and align-items: center; properties to body. Note: Flexbox aligns to the size of the parent container.
    • You can use the vh measurement for the height... Viewport Height handles the sizing of an element in relation to the height of the browser window.
    • Remove all margin from nft-card class
    • Add the status :hover to the image and title elements
    • Try adding a little transition on the element with hover effect

    I hope that helps ;) Keep it up!

  • Ali Mousavi Nizhad•270
    @mnizhadali-afg
    Posted over 3 years ago

    @anoshaahmed - Thank you so much dear Anosha :) And again, the final edit is at github repo! It did not change here :P

  • Anosha Ahmed•9,300
    @anoshaahmed
    Posted over 3 years ago

    Hey good job on this challenge! Have at least one <h1> in your code

    Hope this helps :)

  • Ali Mousavi Nizhad•270
    @mnizhadali-afg
    Posted over 3 years ago

    Thank you so much for feedback. How much should be the value for (vh) in body?

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

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