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

NFT Preview Card Component using SASS

sass/scss
Kevin Copo•150
@snowbot22
A solution to the NFT preview card component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)
Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

  • Yari Morcus•500
    @YariMorcus
    Posted almost 3 years ago

    Congratulations on completing this challenge Kevin!

    I have been taking a peek at your solution, and everything looks very well designed! There are, however, a couple of small things I do want to share with you.

    These points are related to making your design look a little more like the mobile design given to you.

    1. The padding of your section with class .card should be a little larger. I have been trying to figure out the right value, and this should be approximately 2.5rem.
    2. The title (your <h2>) should be a little bigger. You should increase the font size to 2.3rem.
    3. The font-weight CSS property in file _typography.scss on line 8, contains an invalid value. You used the value of light, but I think you meant lighter. The CSS declaration is now invalid due to this mistake.
    4. You should decrease the font size of the .card__review class from 1.8rem to 1.7rem. In combination with font-weight: lighter, the text looks a little more according to the design.
    5. The text in <p> (0.041 ETH) should be a little smaller. I have been trying to figure out the right value, and this should be approximately a font size of 1.7rem The text in <p> (3 days left) and <p> with class .card__div--2__review should not have a font-weight of bold (if I am seeing this right in the design). If you changed the font size of prior point, you should also set the font size on both<p> elements to 1.7rem for consistency.

    The following point is related to your hover state of the image:

    1. You should change your opacity: 0.7 to opacity: .5 (.5 is the same as 0.5). This way, the cube in the image can be seen a little easier (such as seen in the design).

    I also took a look at your CSS, but I am not seeing anything that you should pay attention to.

    I hope you can do something with the feedback I gave you. If you have any more questions, feel free to ask me.

    If I made a mistake somewhere in this post, feel free to correct me and keep building awesome things :D.

  • Kevin Copo•150
    @snowbot22
    Posted almost 3 years ago

    Thank you so much fot the feedback !

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