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

I use css flex box

raymel iznaga rodriguez•240
@rayir03
A solution to the NFT preview card component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Beginner

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

  • Heli0s•670
    @zeerobit
    Posted over 3 years ago

    Well done completing this challenge.. check the link to your github repo i think it's broken i can't open it.. Few points i'd like to share

    -wrap the nft image, the title and the creator name in an anchor tag since they're supposed to be interactive elements

    • under the nft image, add another div with the class name "overlay" add the eye image inside of it then use position absolute to place it on top of the nft-img , change the background color from hsl to rgb so you can add the opacity value to get the transparent effect , it should be like this background-color: rgb(0, 255, 247, 0.4);

    • use more html semantics to wrap your content, example you could use the main tag for ".container" and figure/figcaption tag for ".avatar-container"

    Hope this helps, happy coding!!!

    Marked as helpful
  • Elisavet•500
    @elisavet12
    Posted over 3 years ago

    Hello!!

    This will help you to fix hover states for interactive elements: https://www.w3schools.com/howto/howto_css_image_overlay.asp

    Nice work! :)

    Marked as helpful
  • Account deletedPosted over 3 years ago

    Hello there! 👋

    Congratulations on finishing your challenge! 🎉

    I have some feedback on this solution:

    • Always Use Semantic HTML instead of div like <main> <header> , etc for more info.

    if my solution has helped you do not forget to mark this as helpful!

    Marked as helpful
  • raymel iznaga rodriguez•240
    @rayir03
    Posted over 3 years ago

    Thank you, I have to study more

  • Hexer•3,620
    @EmmanuelHexer
    Posted over 3 years ago

    Great work overall man. Keep it up

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

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