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

NFT Card - almost

11arshaan•20
@11arshaan
A solution to the NFT preview card component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Hello.

I was thinking about using bootstrap for this, but decided to try coding the entire thing. The responsiveness is not how I planned for it to be; I think the bootstrap columns would solve the issue. Or maybe if I used a media query, but what would the settings for the elements be in each query?

Also, what is the recommended method for creating the hover state for the image?

Thank you!

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • Benjamin•130
    @Benjoow
    Posted over 3 years ago

    Hello Arshaan !

    That's a good start :-). You need to focus on css not on bootstrap if you want to be a developper. Take your time and practice your html structure. It's important and your css will be easier to write.

    I use mobile first approche and combinaison of width and max-width property, like this : width: 80% and max-width: (the value of your card component). The idea is to start with mobile resolution and expense your window until deskop resolution. For this exercice you don't need media queries.

    I recommend you to train your responsive with this website : https://courses.kevinpowell.co/conquering-responsive-layouts. It's will more simpler after that :-)

    Marked as helpful
  • Axurynn•200
    @Axurynn
    Posted over 3 years ago

    Good job @11arshaan !

    For the responsiveness, you could use @media queries but you could also use a min-width property. In this case, you could "block" the card width (at 300 px for example) so as it can't go lower. This could fix your responsiveness for the mobile version.

    Overall, you did it well ! Congrats and happy coding 😄

    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

Oops! 😬

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

Log in with GitHub