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

NFT Preview Card Component

Michelle Wangari•50
@Michelle-Wanderi
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 loved this challenge. Polished my css skills.

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • Elaine•11,360
    @elaineleung
    Posted almost 3 years ago

    Hi Michelle, well done completing this, and happy to hear that you loved the challenge 🙂

    I think you did a lot of things well here, such as being able to center the component. There are a few suggestions I have that can help you even in future projects:

    1. Right now in your CSS, there aren't any reset/normalize rules. You'd always want to add these to every project because every browser has its own default styles, and my browser may be different from yours. There should at least be these few rules in every project, and here are some that I use, taken from Andy Bell's CSS reset:

      // put these at the top of your sheet 
      
      *, *::before, *::after {
        box-sizing: border-box;
      }
      
      * {
        font: inherit;
        margin: 0;
        padding: 0;
      }
      
      img, picture, video, canvas, svg {
        display: block;
        max-width: 100%;
      }
      
      html, body {
        height: 100%;
      }
      
    2. Instead of using a width: 40vh on your card, try something like max-width: 400px instead. The reason for that is, if I shrink the browser down, the height of the browser will affect the width, even if I don't change the browser width. Try doing that and see how it affects your card.

    3. I would remove the margins and padding you have on the image and just increase the padding on your card container instead (probably 1.5rem in desktop view and 1rem in mobile). This will make the padding look more even for the text area and the image; this might only work after you've added in the reset rules because there might be default padding and margin on the elements already, so be sure to add those rules in first before trying this.

    Great work, and keep going! 😊

    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