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

responsive display using media queries

accessibility
Kelvin Ginikanna•40
@keltech18
A solution to the NFT preview card component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


  1. I could not add the hover effect on the equilibrium image.
Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • Kent O'Sullivan•1,870
    @12Kentos
    Posted about 3 years ago

    Hey @keltech18 Nice job on completing the challenge!

    I do have a couple of suggestions, first I noticed you did some inline css in the html file, while that's ok for a small project like this, I would suggest avoiding doing that as much as possible. It's really bad practice and will cause a TON of issues for you down the road on future/larger projects.

    Secondly I noticed you selected elements directly like so.

    h1 { font-size: 18px; font-family: 'Outfit', sans-serif; font-weight: 600; color: hsl(0, 0%, 100%); }

    Once again, while this was ok in a small project like this, it will cause a lot of issues and headache in future projects. The problem with this, is the above code won't just affect the h1 of the eth card, you just made but every single h1 on the website. I would suggest in the future giving the element a class, and selecting it that way. It might be a little more tedious but will save you a lot of time in the future.

    Lastly as for you question regarding the hover affect, here is the mdn documentation on the :hover Pseudo class.

    hover

    You can also find a lot of videos on youtube explaining how to use it, this would be your best/easiest way of getting the hover affect you want.

    Hope that helps!

    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 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