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

Responsive NFT card

Paul•70
@Paul-Royce
A solution to the NFT preview card component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


I would really appreciate if someone can give me some feedbacks about my solution. Especially about the css styles that i used, i would like to know if someone can suggest a shorter code that leads to the same outcome.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • bikeinman•1,080
    @BikeInMan
    Posted over 3 years ago

    Paul,

    I think you did a great job already. It took me 150 lines of css. Yours is only at 100. I guess, you are still working on the image hover requirement.

    Good Luck.

    Marked as helpful
  • P
    David Turner•4,130
    @brodiewebdt
    Posted over 3 years ago

    Even small components use a lot of code. I wouldn't worry about it. I would try to stay away from floats. In responsive design they cause troubles because the elements are taken out of the flow of the document. Your hover is missing on the image. The alignment and spacing look good. Nice job.

    Wrap your card div in a Main tag and the attribution div in a Footer tag. Change the Equilibrium text to an H1. Every page should have an H1 for accessibility. You will have to re-style it to match the design.These things will clear the accessibility warnings.

    Download AXE DevTools and you can clear accessibility warnings while you code. https://www.deque.com/axe/devtools/

    Hope this helps.

    Marked as helpful
  • Paul•70
    @Paul-Royce
    Posted over 3 years ago

    Thank you very much David! Your feedback was specific, and above all, constructive!

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

Oops! 😬

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

Log in with GitHub