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

NFT preview card component using Pure CSS

Shiva•670
@shivaprakash-sudo
A solution to the NFT preview card component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Hello everybody,

I tried to implement the coloured hover effect for the image, like shown in the design specs, but I couldn't figure it out, if anyone has any idea on how to do it, please let me know.

Thank you.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Eduardo•910
    @KTrick01
    Posted almost 3 years ago

    Hi! The hover effect can be make easily with an ::after or ::before pseudoelement, here is a quick demo for you using your classes:

    .card__img::after {
      content: "";
      position: absolute;
      background-color: #5bb02c70;
      inset: 0;
      transform: translateX(100%);
      transition: .3s;
    }
    .card__img:hover::after {
      transform: translateX(0);
    }
    .card__img {
    overflow: hidden;
    }
    

    Try it! I hope that it helps you!

    Marked as helpful
  • PhoenixDev22•16,830
    @PhoenixDev22
    Posted almost 3 years ago

    Hello Shiva,

    Congratulation on completing this challenge. Excellent work! I have few suggestions regarding your solution, if you don't mind:

    HTML

    • The attribution should be wrapped by <footer> , it should live outside the <main>.
    • The most important part in this challengeinteractive elements. Since there's a :hover state on the image and means it's interactive, So there should be an interactive element around it. When you create a component that could be interacted with a user , always remember to include interactive elements like(button, textarea,input, ..) for this imagine what would happen when you click on the image, there are two possible ways:
      1: If clicking the image would show a popup where the user can see the full NFT, here you use <button>. 2:If clicking the image would navigate the user to another page to see the NFT, here you can use <a>.

    For the same reason , you can use <a> to wrap Equilibrium #3429.

    • The link wrapping the equilibrium image should either have Sr-only text, an aria-label or alt text that says where that link takes you.
    • For any decorative images, each img tag should have empty alt="" and add aria-hidden="true" attributes to make all web assistive technologies such as screen reader ignore those images in ( icon-view, icon-ethereum, icon-clock ).
    • Profile images like that avatar are valuable content. The alternate text of the avatar’s image should not be Avatar , it’s meaningless. You can use the creator's name Jules Wyvern. Read more how to write an alt text
    • look up a bit more about how and when to write alt text on images. Learn the differences with decorative/meaningless images vs important content
    • If you wish to draw a horizontal line, you should do so using appropriate CSS. You may remove the <div class=”line”>, you can use border-top: to the avatar's part.
    • Adding rel="noopener" or rel="noreferrer" totarget="_blank"links. When you link to a page on another site using target=”_blank” attribute , you can expose your site to performance and security issues.
    • There is a little gap under the image, you should set it display: block;
    • Remember a css reset on every project. That will do things like set the images to display block and make all browsers display elements the same.

    Aside these, Great job on this one. Hopefully this feedback helps.

    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

Oops! 😬

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

Log in with GitHub