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

NFT Preview Card

daniel•80
@retailescapeartist
A solution to the NFT preview card component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


the most difficult thing I found was getting the background to appear over the image when you hover. I had to ask around to get some ideas.

I'm still unsure about how to correctly divide up the sections. I felt that I put a lot of things in here that weren't needed. I will continue to practice these skills.

Any tips on how to separate sections easier is always welcomed.

Everyday is an adventure!

Keep on keepin' on my fellow web devs \o/

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    Daniel 🛸•44,810
    @danielmrz-dev
    Posted over 1 year ago

    Hello Daniel!

    Your project looks great!

    You can separate the sections setting display: grid on your div.card and then using gap to separate them. By using gap, you create an equally sized space between all the elements inside a Grid or Flex container. If you do this, you won't need margins to separate the elements.

    One more suggestion:

    • You can replace your div.container with main.container. This won't change anything visually, but it makes your HTML code more semantic. This improves SEO optimization as well as the accessibility of your project.

    I hope it helps!

    Other than that, great job!

    Marked as helpful
  • Adenuga Abubakr•170
    @abubakr01
    Posted over 1 year ago

    You omitted the two icons towards the end of the design. I mean the eth and the number of days lcons. I wouldn't know whether you forgot to add it or you had some issues with the placement.

    But, lemme just say, you could put them in two separate divs, the you use "display:flex" "Align -items:center"

    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
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