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

NFT Card using grid and flexbox

Bismeet singh•190
@BismeetSingh
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 a relatively easy project, any suggestions to improve are welcome.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Adarsh Rai•560
    @AdarshRai0
    Posted about 3 years ago

    Browser has a default style sheet called User Agent Stylesheet which adds margin to headings and paragraphs and applies font properties to all elements.

    I usually reset all the styles and I start from scratch.

    Here is my styles.css

    :root{
      /* colors and fonts */
      --font: "Montserrat", sans-serif;
      --white: #ffffff;
    }
    
    *{
      margin: 0;
      padding: 0;
      box-sizing: border-box;
    }
    
    html{
      font-size: 62.5%;
    }
    
    html, body{
      height: 100%;
    }
    
    body{
      width: 100%;
      font-family: var(--font);
    }
    
    /* Other rule-sets */
    
    
  • Adarsh Rai•560
    @AdarshRai0
    Posted about 3 years ago

    Hi Bismeet congratulations on your new challenge!

    I took a look at your code and I have some tips for you.

    The ripple background was missing, in this case it is better to import it in the body with background-image and put a media query to change mobile / desktop or use the <picture> tag in the HTML.

    I saw that you used id as a selector, but a good practice would be to handle the entire design with classes and leave the id for forms and Javascript.

    Congratulations, since your first project, your challenges have gotten better and better.

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