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

NFT Preview Card using Vanilla HTML/SCSS

sass/scss
huang-emily•140
@huang-emily
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've been doing Vanilla HTML/CSS for the previous attempts, so I wanted to start learning how to use SCSS to start getting a handle on using more modern ways to write CSS. I ended up really like SCSS since I have a habit of repeating setting CSS properties and not wanting to clean it up after finishing the design, but with SCSS, everything is a lot more condensed and is a lot easier to look through the code.

One thing I did have trouble was keeping the eye view image's opacity at 1 when the hover happens. Any help with that would be appreciated as well as any general feedback with SCSS going forward. Thanks! :)

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Abdul Khaliq 🚀•72,380
    @0xabdulkhaliq
    Posted over 2 years ago

    Hello there 👋. Congratulations on successfully completing the challenge! 🎉

    • I have other recommendations regarding your code that I believe will be of great interest to you.

    SUGGESTIONS 💡 :

    • The .overlay element is just transparent when user hovers the cursor on the image, but the transparency setted for element .overlay also affects it child view-icon's opacity.

    • We can resolve this easily by optimizing the css rules, now add the following rules
    .container-img:hover .overlay {
      opacity: 1;
    }
    
    .overlay {
      background-color: hsla(178, 100%, 50%, 50%);
      transition: 250ms ease-out;
    }
    
    • Explanations for suggestions, we provided opacity: 1 and we have modified the opacity of background-color with the help of hsla color code. So our view-icon will have 100% of opacity.

    • And we add transition from .container-img:hover .overlay to .overlay for hovering state. an important note to remember is we want to add transition on it's normal first then the transition will work out it's triggered state like :hover

    • Because of when we add transition for .container-img:hover .overlay the transition will apply for starting but when :hover state is false then the transition will not work suddenly it will hidden

    .

    I hope you find this helpful 😄 Above all, the solution you submitted is great !

    Happy coding!

    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