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

nft-preview-card-component

Ammar Jalabi•270
@AmmarCode
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'd appreciate it if you can take a look at my solution and give me some feedback. Constructive criticism is what I'm looking for! don't hesitate to be brutally honest :)

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Rio Cantre•9,650
    @RioCantre
    Posted over 3 years ago

    Hello there! Good job in this project. You did well in implementing the design and I would like to suggest the following for you...

    • Add the hover state for the text, for example...
    .card-header:hover {
      color: hsl(178, 100%, 50%);
      cursor: pointer;
    }
    
    .creator:hover {
      color: hsl(178, 100%, 50%);
      cursor: pointer;
    }
    
    
    • Same with the hero image... you should add the hover state with the eye icon

    Hope this helps and Keep going!

  • Naveen Gumaste•10,420
    @NaveenGumaste
    Posted over 3 years ago

    Hay ! Good Job you made it look nearly perfect to the preview

    Keep up the good work!👍

  • Israr khan•60
    @khanisrar
    Posted over 3 years ago

    Awesome

  • Aadvik•1,250
    @Aadv1k
    Posted over 3 years ago

    Hey Ammar, congrats on completing your second challenge on frontendmentor! Here are some fixes you should make to better your site.

    • To create the little hover overflow on the image (as seen in the active-states) you can use position absolute to position an element over the image, with opacity set to 0, then on hover you can maybe change the opacity to 0.5, this is how I implemented the hover effect, you can do it by other means if you feel like it.
    • Add a mobile media query to reduce the width of the container and make the fonts a bit smaller. Ciao ~ Aadvik

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

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