Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 12 months ago

Responsive NFT preview card

bem
Maryam•260
@Maryam1982
A solution to the NFT preview card component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


What are you most proud of, and what would you do differently next time?

Apart from the final hover effect (hover on the image) it was done fast. It took just an hour to put everuthing together of course in hover effect (on the image) I was stuck and 45 mins added to my record.

What challenges did you encounter, and how did you overcome them?

I tried to get the image to fill the container (which itself was inside a flex container). I tried to use object-fit for the image but it was not working until I found out I had to set the height of the image container (flex-basis:3.5 rem) so never forget height 100% is not going to work.

What specific areas of your project would you like help with?

It was just an easy project the challenge and how I managed to solve is mentioned above.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Annalisa•200
    @Annalisa11
    Posted 12 months ago

    Your solution is well done :) The html is well structured with the right use of semantic html tags and the overall look and feel is perfect. I especially like the transition you added on the hover of the image, nice touch!

    The css classes are understandable and named well.

    The only thing I could say something about is the fact that you are using unnecessary css properties sometimes. For example: when using flexbox you always write out the flex-direction: row; even if it is already per default row and doesn't need to be explicitly written out. Same goes for things like justify-content: flex-start;

    Other than that nitpick, nice work!

    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 1st-party linked stylesheets, and styles within <style> tags.

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.

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub