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

NFT Card Design

Jan van Ierssel•20
@Janvampierssel
A solution to the NFT preview card component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Ran into some sizing issues that took me way too long to solve, but at last....

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Rohit Deshpande•870
    @rohitd99
    Posted about 2 years ago

    Hi Jan van Ierssel

    Congrats on completing the challenge.

    I just wanted to point out a few things, which can improve the solution.

    1. I noticed you've used h3 for the title, but an h1 heading would be more suited. For each page a single h1 heading is always expected and all the headings must be in order from h1 through h6. h1 generally goes for the title, h2 for subtitle and so on.
    2. Also on you've put height: 100vh on body , main but min-height : 100vh should be used if you want them to stretch as per content. Although on this challenge it wouldn't make much difference.

    Hope it helps

    Marked as helpful
  • C4rlos•410
    @solracss
    Posted about 2 years ago

    Also this image that have hover action on this suggest that it's clickable element. So it should be link or button.

    For making horizontal line good practice is to use <hr> or just use border-top/bottom of adequate container.

    Images used as icons do not need alt text (ether, clock).

    Overall very nice job! Really like it!

  • Rebecca Padgett•2,100
    @bccpadge
    Posted about 2 years ago

    Hello @Janvampierssel. Congratulations on completing the challenge!! 🎉

    Your solution looks great. I have few suggestions to improve your solution.

    HEADING TAGS

    It is best practice not to skip heading tags in HTML. In future projects just make sure to use headings tags in chronological order.

    • Equilibrium #3429 needs to be wrapped in a h1 tag

    <h1>Equilibrium #3429</h1>

    CSS

    Font size should always be in rem units because pixels is an absolute unit that remains constant regardless of the screen size.

    More info 📚

    Hope this helps you and don't hesitate to reach out to me if you have any questions

    Rem units for font size

  • Michael Johnson•950
    @mikej321
    Posted about 2 years ago

    Hey there,

    Something that I learned that may be of value to you that I got from a book about Tailwind...when it comes to sizing, just attempt to get it as close as you can and go from there. As long as it's close enough, it's fine and not to worry about being 'pixel perfect'. I remember I would do the same, constantly changing values to get it to be exactly the same. It is headache inducing, haha! Hope this is of some value to you and happy coding!

    Michael

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

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