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

nft-prevview-card-component

Simen Hagen•90
@SimenHagen86
A solution to the NFT preview card component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


so my third challenge, feedback is appreciated - maybe on the readme also, how i can improve filling out important info. layout went decent this time - what i had problem was with the preview icon and background overlay. any easier way i can do this?

and still struggling with naming classes - what is recommended naming convensions?

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • PhoenixDev22•16,830
    @PhoenixDev22
    Posted about 3 years ago

    Hello Simen Hagen,

    Congratulation on completing this challenge. Excellent work! I have few suggestions regarding your solution, if you don't mind:

    HTML

    • The link wrapping the equilibrium image should either have Sr-only text, an aria-label or alt text that says where that link takes you (not describes the image).
    • For any decorative images, each img tag should have empty alt="" and add aria-hidden="true" attributes to make all web assistive technologies such as screen reader ignore those images in ( icon-ethereum, icon-clock ).
    • If you wish to draw a horizontal line, you should do so using appropriate CSS. You may remove the <hr>, you can use border-top: to the avatar's part.
    • look up a bit more about how and when to write alt text on images. Learn the differences with decorative/meaningless images vs important content
    • Adding rel="noopener" or rel="noreferrer" totarget="_blank"links. When you link to a page on another site using target=”_blank” attribute , you can expose your site to performance and security issues.

    Hopefully this feedback helps.

    Marked as helpful
  • David•7,960
    @DavidMorgade
    Posted about 3 years ago

    Hello Simen, congrats on finishing the challenge, you did a really good job with the component layout!

    1. I would like to recommend you BEM, is one of the greatest naming convention for vanilla CSS and also one of the best approach when using SASS/SCSS, you will not regret using BEM cause you will always identify your classes and get an unique name on each of them!

    2. Try adding also screenshots of your project into your readme file, you can take screenshots of the current webpage on firefox just by rightclicking and selecting "take screenshot"

    Hope my feedback helps you! good job!

    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