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

NFT preview card component usingHTML, SCSS

Ilia•80
@IliaIvashkevich
A solution to the NFT preview card component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Hi all! How to change background of active image (to Cyan)?

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Naveed•330
    @Naveed89-tech
    Posted over 2 years ago

    You could use overlay with div for color. Before submitting the solution, try to validate your CSS and HTML markup on https://validator.w3.org/#validate_by_upload. To get more ideas, you can check my solution for the same challenge and more.

  • Kehinde•680
    @jonathan401
    Posted over 2 years ago

    Hey @IliaIvashkevich 👋🏽. Congratulations on completing this challenge. To answer your question, you could use two approach to change the background to cyan.

    1. In your html, you could make the div element with class img an overlay, give it a background colour of cyan and when the div is hovered, show the background colour. or
    2. You could use the ::before or :: after pseudo element to create an overlay for the image. I don't know if the above is enough without using a code example though 😆.

    And also,.you could try checking out the accessibility reports to you solution. You could try wrapping the whole elements in a main element. That is <main>{the rest of your html code}</main>. So you should change that <div class="container"> to main.

    You could checkout this freecodecamp article on semantic html.

    Hope you got at least something from this feedback.

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