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

NFT Card built using CSS and HTML

vanilla-extract
Jeremiah Lateef•160
@jeremiahlateef
A solution to the NFT preview card component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


I don't think I have any specific questions but I believe detailing some of the challenges I faced may help another person who may want to attempt the challenge.

  1. Try and learn the basics of properties such as min-height, min-width, and percentages before embarking on the project.
  2. Learn how to center an image.
  3. Learn the basics of CSS Flexbox as you may likely need it.
  4. Use the font-size you're comfortable with.
  5. Always believe in yourself when you experience challenges (I experienced a whole lot but I never gave up).
  6. Breaks are allowed. Don't beat yourself up too much.

I wish you good luck in solving the challenge.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Web Wizard•5,690
    @rsrclab
    Posted over 3 years ago

    Hi, @Jerryl-597 ~

    Congratulate on your solution to the challenge on FM platform. I have studied your work carefully and learned a lot from it. Especially I like the way you did image overlay.

    Here are some of the tips I like to provide.

    1. You can add cursor: pointer to hoverable elements.
    2. Try BEM for structuring elements.
    3. You can add transition on heading and creator name.

    https://www.frontendmentor.io/solutions/my-first-solution-on-chanllenge-V-4IzAivH

    Here is my solution to this challenge, and if it can help you even a bit, it would be happy to me.

    Cheers ~

    Marked as helpful
  • Jeremiah Lateef•160
    @jeremiahlateef
    Posted over 3 years ago

    Thank you so much, Peter, for the awesome feedback. I didn't expect someone to review it so soon. On the second recommendation, I do not know what a 'BEM' structure is. Could you care to elaborate more on it? On the third recommendation, I didn't think it was important to add a transition to both elements, but will now apply it on both elements and on future projects. Thank you for the first recommendation. I really appreciate it.

    Kind Regards, Jeremiah Lateef.

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