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

Full version not perfect made using css and flexbox

karthikeya pvs•190
@karthik5860
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 was not able to make this perfectly so I have lots of doubts they are:

  1. I was not able to change the color of the image when hovered because I was not able to find the blend mode required.
  2. I was not able to put the words in correct place so had to use  
  3. I was not able to link the three hover items so that even if one item was hovered all remaining items will make changes according to the given setting.

Welcome for feedback and if possible can solve my doubts. Thank you

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • SrHatcher•710
    @SrHatcher
    Posted almost 3 years ago

    Hello Karthikeya!

    You are making a great work. don't worry if you struggle making projects. When you struggle it means that you're going the right way to be better in the future!

    Personally i used this setting to make the blue background when you hover the image: Background-color: hsla(178, 100%, 50%, 0.5), you could try it. hsla allows you to use oppaticy in your colors at the final setting: 0.5.

    To use the fonts for the project you can get them from google fonts, i've seen that every project on frontendmentor uses google fonts for the font-family. if you don't know how to use google fonts yet you can watch this tutorial: https://www.youtube.com/watch?v=qgmLDPLApBY

    You can use this CSS rule to make the project more inmersive: cursor: pointer, so that when you put the mouse on something that is supposed to be some kind of link the cursor of the mouse will change to a pointer icon.

    I couldn't understand your third point: I was not able to link the three hover items so that.... if you'd like to explain it again maybe i can help you.

    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