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

Using css to create effects when hovering over the image.

Amhed Hussien•390
@Eng-Ahmed-Hussien
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'm most proud of the hover effect on the NFT image, which smoothly reveals an overlay and an eye icon when the user hovers over it. This adds a nice interactive touch to the component.

Next time, I would experiment with CSS animations or transitions to make the hover effect even smoother. I might also explore using JavaScript for more advanced interactions, like a subtle zoom-in effect or a delay before revealing the overlay.

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

One challenge was making the hover effect work correctly, ensuring that the overlay and the view icon appeared at the right time. Initially, the overlay wasn’t showing because display: block didn’t take effect properly. I resolved this by using opacity and visibility instead of display: block, allowing for smoother transitions.

Another challenge was positioning elements within the card while keeping the layout responsive. I adjusted the flexbox properties and fine-tuned padding/margin values to ensure consistency across different screen sizes.

By testing on multiple screen sizes and tweaking the CSS, I managed to create a balanced and visually appealing design.

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

Hover Effect Improvements:

Would using CSS transitions or keyframe animations improve the hover experience? Is there a better way to handle the hover effect without using .img-box:hover .view-icon selectors? Accessibility & User Experience:

Should I add ARIA attributes to improve accessibility for users who navigate without a mouse? Are there any improvements I could make for keyboard navigation and focus states? Code Optimization:

Is my approach to the hover effect the most efficient, or is there a cleaner way to achieve the same result? Would using CSS variables improve the maintainability of my styles?

I appreciate any feedback to refine my project further! 🚀

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on Amhed Hussien's solution.

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.