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

NFT preview component

bem
Dharmik_487•1,740
@Dharmik48
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 was the first project of mine in which I used the BEM naming convention, checkout it possible and give you feedback

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Aakash Verma•9,500
    @skyv26
    Posted over 3 years ago

    Hi! Dharmik, you checked you design and design responsivess and I have noticed some issues.

    1. First of all, the most important work you left undone is, image hover effect. I would suggest you to implement the hover effect code, because it is the challenge's requirement, so always stick with the requirement.

    2. You can clearly see that your small icon, etherium 0.041ETH text and time left text are not aligned with their respective icon. It seems perfect if we see it from really far distance or small laptop screen, but not on big screen or closer look.

    Tip

    Update your CSS rule

    .nft__price {
        color: hsl(var(--clr-cyan));
        font-weight: 700;
        display: flex;
        align-items: center;
    }
    
    .nft__time {
        font-weight: 400;
        display: flex;
        align-items: center;
    }
    
    1. As I figured out while checking your 2. issue and I found that you have used font-awesome icon rather that than images provided by FEM. It is totally ok, that you have just completed your work with ease but you also missed , great learning opportunity too. You can still work on this and change your code and use that images instead of Font-Awesome icons.

    Overall Really nice work, your design is responsive too. I hope you you will soon update your code.

    Best Wishes

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

    Hey good job on the challenge! In the future, to avoid accessibility issues, include at least one <h1> in your code. Also, remember that <section> usually needs a heading, so if you don't need a heading in it, use some other element such as <div> :)

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