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

NFT Preview Card Component

Dicskson Owusu Nyantakyi•270
@ondickson
A solution to the NFT preview card component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Overall, I'm happy with how this turned out. I'm glad I could solve the issues in my previous challenges and actually be able to understand what each code does in the code.

I was finding it difficult to make my card size fit on the page without scrolling down or zooming out. After a night of watching tutorials, and listening to the feedback from my previous challenges. Everything became so clear and understandable.

PLEASE ANY SUGGESTION IS HIGHLY APPRECIATED. I'M LOVING THIS COMMUNITY AND THE HELP I'VE RECEIVED THROUGH YOUR FEEDBACK. Thank you

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Lucas 👾•104,160
    @correlucas
    Posted about 3 years ago

    👾Hello Dicskson Owusu, congratulations for your new solution!

    🎉 Nice solution and nice code! I can see that you paid a lot of attention to your code/design. If you don’t mind I’ve some tips for you:

    1.Add transitions to make smoother the interaction while the element gets hovered, you can use a value like transition: all ease-in 0.5s.

    2.Add a margin of around margin: 20px to avoid the card touching the screen edges while it scales down.

    3.The correct value for this shadow is box-shadow: 5px 5px 15px 5px rgb(0 0 0 / 3%);

    4.You can create a media query to save space in the author section to make each information in a different row. Here’s the code for this media query.

    @media (max-width: 350px) {
    .author {
        color: var(--Softblue);
        display: flex;
        font-size: 15px;
        align-items: center;
        justify-content: left;
        flex-direction: column;
    }
    }
    

    ✌️ I hope this helps you and happy coding!

    Marked as helpful
  • romila•3,550
    @romila2003
    Posted about 3 years ago

    Hi @ondickson,

    Congratulations 🎉 for completing this challenge, your card looks great, and you have used the right semantics. Also you have no accessibility and HTML issues which is great too.

    1. The only thing I would suggest is to you use min-height property to center the card in the middle e.g. min-height: 100vh;
    2. Also, in the design, the word 'Equilibrium' and the profile's name has a hover effect which are shown in the design provided. I would suggest you wrap it within the a tag since if this was a functional NFT card, those texts would redirect you to external/internal websites.

    Overall, great attempt and wish you the best for your future projects so keep coding 👍

    Marked as helpful
  • Dicskson Owusu Nyantakyi•270
    @ondickson
    Posted about 3 years ago

    Thank you very much for the feedback. I will fix these issues right away.

    Edit: I noticed all the minor details. got really excited and totally missed them all but I've fixed everything. I want to hear your feedback once again. That was very 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

Oops! 😬

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

Log in with GitHub