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

NFT Preview card - Using CSS3's Grid & Flex

accessibility
Abdul Khaliq 🚀•72,380
@0xabdulkhaliq
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 everyone..👨‍💻

  • This was an excellent challenge to train and improve my knowledge with grid & flex layout.
  • This helps me to practice about turning designs into actual website
  • I tried to make my code as clean and readable as possible! If there's anything I can improve on this, I'd love to know!

Feel free to leave comments on how I can improve my code.

Peace be upon you..✨

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Pirate•170
    @ima9gh
    Posted 11 months ago

    Hi please help me.

    What is the problem with my code, why doesn't it work? Although the opacity on hover is 1!

    The eye is the icon on the photo when hovering

    .NTF .eye{
    position: absolute;
    background-image: url(images/icon-view.svg) no-repeat center;
    background-color: var(--clrBGeye);
    width: 290px;
    height: 290px;
    display: flex;
    justify-content: center;
    align-items: center;
    top: 130px;
    border-radius: 5px;
    opacity: 0;
    }
    
    .NTF .eye :hover{
    opacity: 1;
     }
    

    : I haven't uploaded the challenge yet.

  • Hassia Issah•50,390
    @Hassiai
    Posted over 2 years ago

    Increase the width of .container to get the desire width in the design. for mor responsive width use max-width instead of width. There is no need for height value in .container the padding value is sufficient.

    Use rem or em as unit for the padding , margin, width and preferably rem for the font-size for more css units this watch this https://youtu.be/N5wpD9Ov_To

    Hope am helpful

    Well done for completing this challenge,

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