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

Mobile-first solution using HTML/SASS/CSS

sass/scss
DkP-Consult•60
@DkP-Consult
A solution to the NFT preview card component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Hello,

I do my second challenge on Frontend Mentor. But, it was difficult to do the :hover section. I'know, had a littre difference for the icon in price & clock. I'll fix that soon.

Code review appreciate !

Thanks !

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • Danilo Blas•6,300
    @Sdann26
    Posted about 3 years ago

    Hi DkP!

    I would recommend you to eliminate the margin in the div with the class .card because it is not a good way to center an element, because at the end it is not centered vertically for all type of screen only for the one you occupy, so to the body you can add the following:

    body {
        display: flex;
        justify-content: center;
        align-items: center;
        min-height: 100vh;
    }
    

    With this you center it both vertically and horizontally and set a minimum height so that it is always centered in the middle vertically.

    This is the only thing I can recommend, if you can generate a new report after you have made the changes written in the previous comment so that you do not get any errors in the report.

    Good Coding!

    Marked as helpful
  • Ahmed Bayoumi•6,680
    @Bayoumi-dev
    Posted about 3 years ago

    **Hey!**Congratulations on completing this challenge... You have some accessibility issues that need to fix.

    • Document should have one main landmark, Contain the component with <main>.
    <main>
       <div  class="container">
          //...
       </div >
    </main>
    
    • Page should contain a level-one heading, Change h2 to h1 You should always have one h1 per page of the document.
    • All page content should be contained by landmarks, Contain the attribution with <footer>.
    <footer>
       <div class="attribution">
          //...
       </div>
    </footer>
    

    I hope this is useful to you... Keep coding👍

    Marked as helpful
  • Abdul•8,560
    @Samadeen
    Posted about 3 years ago

    Hey!! Cheers 🥂 on completing this challenge.. .

    Here are my suggestions..

    • You should use <main class="card"> instead of <div class="card">.
    • Go down orderly when you are using the headings h1 down to h2 down to h3 and so on.
    • You can wrap your attribution section in a footer tag to avoid accessibility issues.

    This should fix most of your accessibility issues

    . Regardless you did amazing... hope you find this useful... Happy coding!!!

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