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

NFT preview card component using SCSS

sass/scss
Tabassum Khanum•110
@tabassum2507
A solution to the NFT preview card component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Any feedback or improvement tips are always welcome and appreciated!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

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

    Hello @abassum2507 ,

    I have some suggestions:

    • By using landmark elements , you can improve the navigation experience on your site for users of assistive technology . So wrap the content of the body (card) in<main>, a< footer >for the attribution.

    • It's invalid html to wrap a heading element in an anchor tag. Swap those around so the anchor is inside the heading.

    • Try flexbox properties and a min-height 100vh on the main to center the card.

    • The eye image doesn't really need to be in the html, you could do it with css.

    • The images don't need filled alt. They are decorative images, so alt attribute should be left intentionally blank. You can optionally addaria-hiddenor role presentation to ensure the images are always ignored by screen readers EXCEPT avatar read up about how and when to write alt text

    • You can simply use unordered list <ul> to wrap <div class="box__price">and in each list item would have <img > and <p>.

    • You should use em and rem units .Both em and rem are flexible, scalable units which are translated by the browser into pixel values, depending on the font size settings in your design. Using px won't allow the user to control the font size based on their needs.

    • It's rarely a good practice to set heights on elements . Let the content dictate how tall something needs to be.

    • Use max-width instead width: 350px;

    hopefully this feedback helps.

    Marked as helpful
  • Rio Cantre•9,650
    @RioCantre
    Posted over 3 years ago

    Hello there! Nice job making this project. Viewing your solution I would suggest the following for you...

    • Adjust the top margin on the main content into margin-top: 5rem;
    • Same with the hover icon, adjust the properties for example...
    .box__img2 {
      position: relative;
      top: 25px;
    }
    
    • Wrap the box with specific tag like main and attribution with footer tag
    • Use a validator to check your solution before submitting

    Hope this helps and keep up the good work!

    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

Oops! 😬

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

Log in with GitHub