Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 5 months ago

NFT Preview Card Component built with HTML and SCSS

sass/scss
P
Shakira Reid - Thomas•150
@KaeTheDev
A solution to the NFT preview card component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


What are you most proud of, and what would you do differently next time?

I am proud of my ability to use Figma to understand how the styles should work. In previous projects, the Figma files included a detailed style guide, but this one was more limited. This challenged me to improve my skills in interpreting a Figma file and translating it into a functional design.

What challenges did you encounter, and how did you overcome them?

This project was fairly simple, and I chose it intentionally to get more practice with HTML and SCSS while studying responsive design in more depth. However, implementing the hover effects—especially the overlay—presented a learning opportunity. I overcame this challenge through trial and error, as well as by reading through documentation to better understand how to achieve the desired effect.

What specific areas of your project would you like help with?

I would appreciate any and all feedback. I’ve been learning so much from the community here and would love to hear suggestions on how I can improve further.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Marzia Jalili•9,710
    @MarziaJalili
    Posted 5 months ago

    Awesome work!

    A cherry on the top?

    • For the smoother color of the heading and the link you can use the transition property:

    Take the code below as an example:

    transition: color 0.5s; /* or .5s for short */
    

    This ensures that the colors will change after 500 milliseconds which makes it look even better.

    Great job overall, keep up the grind!

    😁😁😁

    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

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