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

NFT Card component

Vincent Daniel•410
@davinceey
A solution to the NFT preview card component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Wheew! Finally learnt how to use the pseudo classes in accomplishing wonderful transitions and hovering effects. Your feedback on areas of improvements would be sincerely appreciated!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Elaine•11,340
    @elaineleung
    Posted almost 3 years ago

    Hi Vincent Daniel, great job in putting this together and especially in learning to use pseudo classes! 😊 I think this is a good attempt in positioning elements, and I would say the next thing to work on is how to make this component responsive. There's a lot of fixed widths used and even padding for positioning, which makes it difficult for the browser to resize the component at smaller browser widths. I tried in the inspector just now to see how I change some of these properties, and I still can't make the component responsive. For instance, for the first-span and second-span, they are separated by a 4.75em of padding, meaning that gap is fully filled with a fixed padding and cannot be changed. To separate them, I would use flexbox instead and would use justify-content to keep them separated, as that way, the gap between them is flexible and the component can also be resized.

    In short, I recommend using responsive properties such as max-width and to be less reliant on using fixed widths for positioning. To see what I mean about responsiveness, you can have a look at my solution here and resize the browser width to see how the component responds.

    I do think you did well here on the whole in building this, well done!

    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

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