Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted about 1 month ago

NFT Preview Card Component – HTML & CSS Solution

neeta Purohit•160
@neetaPurohit
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 achieving the exact design with proper alignment and smooth hover effects. Next time, I would use semantic HTML tags for better accessibility.

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

One challenge was aligning the icons and text properly in a single line with equal spacing. Another major challenge was creating the image overlay effect with the eye icon on hover. Initially, the overlay didn’t cover the image perfectly, and the eye icon wasn’t centered. I solved it by using position: absolute and proper z-index inside a relative container. After a few layout adjustments and testing, everything started working smoothly.

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

I'd like feedback on improving the image hover effect and making the layout more responsive. Also, suggestions on better semantic HTML structure or cleaner CSS practices would be helpful.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Md Irfan Rahman Mubin•210
    @Md-Mubin
    Posted about 1 month ago

    You can handle that border without using a extra div that you used class name "line". Use padding insted of margin in user classname and than use "border-top : 2px solid #(your color)" to get that line desgin.

    Marked as helpful
  • Alaa Mekibes•2,060
    @alaa-mekibes
    Posted about 1 month ago

    Great work just a few points to fix:

    • Use Only One <h1> Per Page

    Maintain a proper heading structure, using <h1>, <h2>, and <h3> in a hierarchical manner. This improves both organization and SEO.

    • Never Leave the alt Attribute Blank

    Always provide a meaningful alt description for images. This improves accessibility and contributes to better SEO.

    • Use semantic HTML elements for better structure and accessibility. For example:
    <body>
        <main>
            <!-- Your code -->
        </main>
    </body>
    
    • Use min-height: 100vh to get full-screen.

    Impressive work, stay focused and keep excelling!

    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