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

NFT - Preview Card

accessibility, sass/scss
Avinash DV•150
@avinashdv
A solution to the NFT preview card component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Had a lot of fun & a little bit frustration for achieving the background pixelated shadow. I've tried various combinations and finally settled down to one. Tried the background-blend property in hover state with multiple bg-imgs and bg-color. Overall this project helped me learn something new.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Christian Prasetya•370
    @christian-prasetya
    Posted over 2 years ago

    Congratulations for your solution, it's very nice.

    1. I see you try to use BEM Method for the CSS styling, which is great, but I think there some area of improvement.
    <div class="nftCard__author">
              <img
                class="nftCard__author__avatar"
                src="./assets/images//image-avatar.png"
                alt="author image"
              />
              <p class="nftCard__author__about">
                Creation of <span class="nftCard__author__name">Jules Wyvern</span>
              </p>
            </div>
    

    I think it will be better and will be more easy if you write like this:

    <div class="nftCard__author">
              <img
                class="nftCard__author-avatar"
                src="./assets/images//image-avatar.png"
                alt="author image"
              />
              <p class="nftCard__author-about">
                Creation of <span class="nftCard__author-about-name">Jules Wyvern</span>
              </p>
            </div>
    

    especially when you use scss, it will make your life easier, so basically you can use nesting selector from Scss like this:

    .nftCard__author {
         &-avatar {}
         &-about {}
    }
    

    which will make your life easier when writing the scss code.

    1. I appreciate you try to use Scss, but I think you can improve by folder structuring your scss partial file (it will be very helpful), and create component-like scss file.

    Read this if you don't mind

    1. Try broadening your scss file with @mixins, function, and many more, to unlock the potential of your scss/sass skill. Sass - Guide

    Hope this will help, and I'm sorry if my english little bit bad.

    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