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

Solution to NFT Preview Card Component Challenge

Alex Fernández•40
@Arekkusu17
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 c: , this is my second challenge. Any kind of feedback is appreciated. In the next days, I am going to polish more the stylesheet because i feel some of the styles used are a little redundant between already inherited properties. So I will take a look on that.

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 @Arekkusu17 ,

    I have some suggestions regarding your solution:

    • Using landmark elements , you can improve the navigation experience on your site for users of assistive technology . So use a <footer >(for the attribution)

    • Anything with a hover style in a design means it's interactive, you need to add an interactive element<a> around the image and Equilibrium #3429 and Jules Wyvern

    • For any decorative images, each img tag should have empty alt="" and aria-hidden="true" attributes to make all web assistive technologies such as screen reader ignore those images .Read about how and when to write image alt text and what it's for.

    • The link wrapping the original image either should have Sr-only text, an aria-label or alt text that says where that link takes you.

    • The eye image doesn't really need to be in the html, you could do it with css. If you want it to stay in html it needs to be aria-hidden .

    • You can simply use unordered list <ul> to wrap .information and in each list item <li>would have <img > and <p> for the text .And for each <li> , you can give :

        display: flex;
        align-items: center; /* align them on the center */
        justify-content: flex-start;
    
    

    Then a little margin to the img or the p .(no need for <h2>)

    • you can add this to fix the the little quirk of the overlay
    .nft-image {
       border-radius: 0.9rem;
       /* max-width: 19rem; */
       width: 100%;
       **display: block;**
    

    Also

    .creator img {
        width: 2rem;
    }
    
    
    • Use flexbox properties to center the card on the middle of the page to the element that holds the card and min-height: 100vh; .
    {
    display: flex;
    align-items: center;
    justify-content : center ;
     flex-direction: column;
    min-height: 100vh
    }
    

    Hopefully this feedback helps.

    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