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

NFT Preview Card

João Gabriel•340
@joaojgabriel
A solution to the NFT preview card component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


  • how to add the white border to author's avatar?
  • how to align the text vertically to the center of the icon in :before?

any other feedback welcome

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • Esteban•150
    @ehmenzala
    Posted almost 3 years ago

    Hello João!

    For the white border on the avatar (and actually with any other element that you want to have it)...

    • You should add border-radius: 50%; property, and then the border: 1px solid #colorThatYouWant; directly on your image. And you’ll have your fancy circular border.

    For the ethereum icon...

    • Personally, I think you should turn the <span class="price"></span> position to relative. This is because you will also define its :before pseudoelement position to absolute. Then you could play with left padding on the <span class="price"></span> and inset properties (top, right, left, bottom) on its :before pseudoelement.

    I hope this can help you! And keep it up 👋

    Extra tips...

    • In the title of your card, when you put the cursor to the right of it —without touching any of its characters—, the :hover event is fired on the title (the light blue colour is applied to the title). To avoid this I suggest that in your <h1></h1> you set the width: max-content; property so that the :hover is only applied when you point the cursor over the letters of the title, but not to the sides.

    I leave you a link to the official documentation of the max-content property in case you want to take a look...

    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