Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted over 1 year ago

Artistic HTML/CSS NFT Preview

Bhavya Khatri•40
@bk408
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 everyone,

I'm excited to share my latest project with you all - the "NFT Preview Card" created using HTML and CSS. This project allows me to showcase my skills in web development and create an appealing preview card for digital collectibles. I would greatly appreciate your feedback and insights to help me improve this project further.

What I'd Like Your Feedback On:

Design and User Experience: What are your thoughts on the overall design and user experience of the NFT preview card? Is it visually appealing and easy to navigate?

Code Structure: Are there any specific areas of my code that you find unclear or could be improved for better readability and maintainability?

Browser Compatibility: Have you tested the project on various web browsers? Are there any compatibility issues I should be aware of?

Best Practices: Are there any best practices in HTML and CSS that I may have overlooked? Any suggestions for optimizing the code or improving efficiency?

Content and Information: Is the content displayed on the NFT preview card clear and informative? Is there any additional information or metadata you would suggest including?

General Feedback: Any other thoughts, suggestions, or feedback you have about this project are highly welcome!

Your insights will be invaluable in refining this project and making it even better. Thank you for taking the time to review and provide feedback!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on Bhavya Khatri'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 1st-party linked stylesheets, and styles within <style> tags.

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.