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

NFT Card using HTML and CSS only

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

Solution retrospective


Please share your thought on how to improve this...

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Vanza Setia•27,715
    @vanzasetia
    Posted over 3 years ago

    Hi there! 👋

    Congratulations on finishing this challenge! 👏

    I have some feedback on this solution:

    • Accessibility
      • Well done on using landmarks correctly! 👍
      • Use interactive elements (a) for any elements that have :hover or :active states.
      • Always wrap text content with a meaningful element (p).
      • For decorative SVGs, add aria-hidden="true" attribute to the svg.
    <svg aria-hidden="true">
    </svg>
    
    • Alternative text for images should not contain any words that related to image (e.g. picture, photo, logo, icon, graphic, avatar, etc). It's already an image element so the screen reader will pronounce it as an image. 🙂
    • The alternative text for images should not be hyphenated.
    • Use the creator's name as the alternative text for the avatar.
    • Use rem or sometimes em unit instead of px. Using px will not allow the users to control the size of the page based on their needs.
    • Styling
      • I would recommend using flexbox to align the icon and never use inline styling. It has a high specificity and can cause a serious issue on bigger projects.
      • I would recommend making the body element as a flexbox container to position the card in the middle of the page, both vertically and horizontally. Then remove all the margin properties from the container element.
    /**
     * 1. Make the card vertically center and
     *    allow the body element to grow if needed
     */
    body {
      display: flex;
      align-items: center;
      justify-content: center;
      min-height: 100vh; /* 1 */
    }
    
    • Best Practice (Recommended)
      • Remove the xmlns attribute from the inline SVG. It doesn't need it by the browser.

    That's it! I hope this helps! 😁

    Marked as helpful
  • Account deletedPosted over 3 years ago

    Hi there 👋

    Congratulate on finishing your project 🎉. You did a great job 💡

    I give some suggestions to help you take your project design to the next level 📈😉

    • Add box-shadow to the card
    • Change the h1 font-size to 24px
    • Add cursor: pointer to the h1 and .creator-name elements

    Happy coding ☕

    Maqsud

    Marked as helpful
  • optimusprime202•1,160
    @optimusprime202
    Posted over 3 years ago

    Hey @ckullo, You’re on the right track now.

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

Oops! 😬

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

Log in with GitHub