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

Nft Preview Card Component

accessibility
Daud Ismail Olakunle•20
@Eminentdio
A solution to the NFT preview card component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


My problem in coding lies with rendering my webpage appropriately in mobile view. Is there anything I need to know specifically to solve that?

I have always been having a kind of feeling of not having enough knowledge of any language before embarking on another one even if I can answer or practice any damn concept on it. Please is there a cure to this kind of syndrome?

Please, don't forget to criticize this project as well. The last one helped me to improve on some things like designing for Screen Readers.

Thanks!!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Lucas 👾•104,160
    @correlucas
    Posted almost 3 years ago

    👾Hello Daud Ismail, congratulations for your new solution!

    🎨 Here’s some tips to improve your component design:

    Make the shadow smoother reducing its opacity, see a good value for this shadow: box-shadow: 9px 4px 9px 4px rgb(0 0 0 / 4%);

    To improve the solution responsiveness, make a media query to break the elements in the pricing section after width: 350px and make every content in a different row, saving space for low resolution devices.

    @media (max-width: 350px) {
    .details {
        display: flex;
        justify-content: space-between;
        align-items: center;
        padding: 4px;
        border-bottom: 2px solid hsl(215, 32%, 27%);
        flex-direction: column;
    }
    }
    

    ✌️ I hope this helps you and happy coding!

    Marked as helpful
  • Sankalpa Sarkar•520
    @IllusiveCoder1101
    Posted almost 3 years ago

    Congrats on completing the challenge, about the mobile display issue, I think you should look into css media queries which is responsible for display on different screen sizes. Keep up the great work!!!!

    Marked as helpful
  • Talha Khalid•200
    @talha-007
    Posted almost 3 years ago

    Use divs and h1 tags only instead of span. you can use a div to overlay on the image which shows that eye icon. give it styling of hidden and when you hover give it a display. and you'll learn by the time don't worry it's good.

    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

Oops! 😬

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

Log in with GitHub