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

NFT preview card component solution

Jack Shelton•210
@thejackshelton
A solution to the NFT preview card component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


This is my first ever project, and I can tell that I made a decent amount of mistakes. How do I get the image to display the icon with the background changed at the same time?

I also had a lot of trouble getting some parts of the card inline with each other. Is there a better way to go at it then the way I implemented?

I started my web development journey a week and a half ago, and would love some feedback on how to avoid redundancy in my code, make it easier, and some alternative ways I could've gone at it.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • AgilitiesZ•310
    @phichayut-pak
    Posted about 3 years ago

    Hi! I would say it's a great start for you! But first of all, congratulations on your project! 🎉🎉 Here are the things I would suggest :

    1. For your question, I fixed it by playing with opacity on hover. You might wanna try that out, or another way is to use group and group-hover from TailwindCSS ( it's a css framework that pretty much makes our styling quicker and easier )

    2. You might be using padding without noticing that the overflow on x axis appears. Take a deep look on this, it'll affect a lot when you're working with different designs.

    3. Font size and Font weight matter! You can choose whether you want to fix on this one, it's just for more detail.

    Keep studying and practicing! 🔥🔥

    Marked as helpful
  • Ginaldo Capistrano•70
    @gcapistrano
    Posted about 3 years ago

    Hi, @thejackshelton! Great start! I'm also a beginner, but I'd like to suggest a way to display challenges that I had used. I displayed challenges sorting by easier first and filtering, in my case, by checking free, newbie, and HTML & CSS options. There are ten of them by now. I intend to go through each one, easiest to hardest. Maybe you had already made this procedure, but it could be useful anyway. Keep coding!

    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
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