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

Responsive NFT card preview.

foundation
Adil Rafiq•120
@Adil-Rafiq
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 People! So this was my first challenge project from this website. Even though the project was quite easy but as a beginner, I find it some how difficult. The most tiring part of this project was alignment of elements. And there is a part where I have to align clock icon with its text but neither the margin nor the padding option was working. I would be glad if someone can guide me through this.\

Thank you.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Karishma Garg•1,010
    @karishma-dev
    Posted about 3 years ago

    Hey, your solution looks good. Few suggestions:

    1. Make your container as the main tag instead of div, this should help you solve your accessibility issues.
    2. And for the alignment of elements issue that you are facing, I used flex in my solution. Add flex in your left and right class, and also the class that contains both of these classes.

    Hope this helps you!

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

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

    Lets firstly work on your accessibility issues.

    • Document should have on main landmark basically means your html should be structured more semantically and the correct format should be your <header>......</header> followed by your <main>......</main> and lastly your <footer>....</footer> hence you should use <main class="container"> instead of <div class="container">.
    • Page should contain a level-one heading basically means your html should have a h1 it aid navigation hence <p >Out Equilibrium collection promotes balance and calm </p> should be <h1>Out Equilibrium collection promotes balance and calm</h1> and you should also go down orderly when you are using the headings h1 down to h2 down to h3 and so on.

    This should fix most of your accessibility issues.

    • You can maybe increase the font size of your a tag and pad out some of your items.

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

    Marked as helpful
  • Tesla_Ambassador•3,070
    @tesla-ambassador
    Posted about 3 years ago

    Hey Adil, Congrats on completing your first ever frontend mentor challenge. It looks pretty sharp too! Here's a few tips:

    • First off, to answer your question, you might want to wrap the clock icon and it's text in a div and apply the following properties to the div (let's give it a class of "clock-div" I am not good with names):
    .clock-div {
        display: flex;
        align-items: center;
        gap: 10px;
    }
    

    It's the align-items: center property that does the magic!

    • You also need to place landmarks in your html code so that it's well structured and easily navigated by the browser This will fix your accessibility issues. follow this link to learn more about landmarks and how to use them. Happy Coding!
    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