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

nft-preview-card-component using Sass

sass/scss
Efosa Collins EVBOWE•365
@efecollins
A solution to the NFT preview card component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Yes, the part where you hover on the img-equilibrium for a cover and a img-view to display was so difficult. Help, please?.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Rio Cantre•9,650
    @RioCantre
    Posted about 3 years ago

    Hello there! Great work with this one. Regarding the solution you submitted, I think you should know the following notes…

    • To understand more about the hero image hover state, refer it with this example Overlay in Image (If this is still applicable)
    • This line <div class=" attribution"> can be wrap with footer tag or placed it inside the main tag
    • Clean the whitespaces in the code
    • Adjust the margin in main #card ruleset into margin: 10rem auto; and remove the margin placed on the media query
    • Add cursor: pointer for the hover state of the design
    • Increase the font size of h1 into font-size: 22px;

    In the brighter side...

    • Well done with the hover state of the design, specially the hero image
    • The project is responsive and utilized the details based on the original design
    • Great job in using Sass for styling, the compositions are well organized
    • The HTML structure is well organized and readable

    Above all, The project is awesome! Keep it up!

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 1st-party linked stylesheets, and styles within <style> tags.

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.

Oops! 😬

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

Log in with GitHub