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

NFT PREVIEW CARD COMPONENT

wisdom•10
@wisdompython
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 need some help with using box shadow for this code And also some helping in reducing the thickness of an horizontal line

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Remus D. Buhaianu•3,125
    @remusbuhaianu
    Posted over 3 years ago

    Hey @wisdompython , good job on completing this challenge!

    I had a look at your final solution and I have a few suggestions that I hope will be useful to you:

    • Don't use a fixed height on your card element, especially not with an absolute unit such as px. Your layout should be built around the available content.

    • Set min-height: 100vh on your body element if you want to center vertically and horizontally everything inside it.

    • Wrap your card inside a <main></main> element to remove some of the errors from your report

    • Add the alt attribute to your img element - if the img is just for decorative purposes, then you can simply write alt=""

    • The 2 text hover effects and the image overlay hover effect are missing from your solution. Consider implementing them using the :hover pseudo-class https://www.w3schools.com/cssref/sel_hover.asp

    • You don't need an hr to create that line. You can set a border-top property on your footer and then also add a padding-top to push the line away from the content

    Hope my suggestions will be useful to you. Keep up the good work!

    Marked as helpful
  • Abhik•4,820
    @abhik-b
    Posted over 3 years ago

    👋 Hello Wisdom , Your solution is nice & I liked it . However I have some suggestions that might make this solution even nicer :

    • body should have min-height : 100vh; so that the card is in the center of screen
    • using px values as border-radius can make the card a perfect rounded corner rectangle
    • removing border-style:solid; in card-body make it look better
    • you can play with the box shadow values of card-body to produce a nicer shadow
    box-shadow: 0px 0px 10px hsl(217deg 78% 5%), 0px 10px 10px hsl(216deg 50% 16%), 0px 20px 20px hsl(217deg 78% 5%), 0px 0px 10px hsl(220deg 55% 22%);
    

    Other than those your solution is good enough , Please keep up with this good work 👍

    Marked as helpful
  • PerfectPixl•20
    @PerfectPixl
    Posted over 3 years ago

    Hey @wisdompython! Great job! Keep coding! Improve your web developer skills. What about h1:hover {color: anothercolor;} ? Please see design files of your challange. Wish you happy coding!

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

Oops! 😬

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

Log in with GitHub