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

NFT Preview Card Category (HTML | CSS | JS)

Sahil Kumar•190
@Vi-r-us
A solution to the NFT preview card component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


NFT Preview Card Category

I created an NFT preview card component, featuring a modern UI design that is responsive across various screen sizes. This project was developed as part of the Frontend Mentor challenge. To ensure responsiveness, I utilized a flex layout combined with media queries. Additionally, I enhanced the loading experience with webkit animations and implemented Lottie animations using JSON files.

Table of contents

  • Overview
    • The challenge
    • Screenshot
    • Links
  • My process
    • Built with
    • What I learned
    • Useful resources
  • Author

Overview

The challenge

During this project, I encountered several challenges, including handling different images for desktop and mobile views. To address this challenge, I implemented image selection with media queries. Additionally, I delved into the basics of webkit animations and their functionality, as well as learned how to incorporate JSON file animations using Lottie.

Screenshot

Desktop Design | Mobile Design :-------------------------:|:-------------------------: |

Links

  • Solution URL: GitHub Repository
  • Live Site URL: Deployed on Github pages

My process

Built with

  • Semantic HTML5 markup
  • CSS custom properties
  • Flexbox, Grid Layouts
  • Pseudo-elements, Transform
  • KeyFrames Animations
  • Lottie Animations (JSON)
  • Mobile-first workflow

What I learned

This project provided valuable experience in front-end development, particularly in achieving responsive design using flex layouts and media queries. It also expanded my knowledge of webkit animations and the implementation of JSON-based animations with Lottie.

Useful resources

In completing the challenges of this project, I found the following resources particularly helpful:

  • Kevin Powell's Video on Animations - Kevin Powell's video provided valuable insights into the basics of animations and how to apply them effectively.
  • Resource on Animation Basics - This resource helped me grasp the fundamentals of animations and apply them to this project.
  • Playlist on Pseudo-elements - This playlist was instrumental in understanding and using pseudo-elements to enhance the project's UI.
  • Implement LottieFiles Animations

Author

  • Github - vi-r-us
  • Frontend Mentor - @Vi-r-us
Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • The Bipu•430
    @the-bipu
    Posted almost 2 years ago

    Hey Buddy !!

    1. Don't ever paste the readme content in the community feedback section. If you have any question then you can ask freely to the community.
    2. Font sizes are given in the style-guide.md file.

    Other that these everything in the project is fine. Also the animations are truly impressive.

    Happy Coding !!

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