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

NFT preview card using css and html

Aviraj Walunj•80
@avirajwalunj
A solution to the NFT preview card component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


This is my first project and spent about a day figuring this out. my question is what problems do you see in my code and on what things should i focus? i am lacking at understanding position tab and i feel like i just used same thing everywhere? feel free to give any opinion. thank you in advance.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • darryncodes•6,350
    @darryncodes
    Posted over 3 years ago

    Hi Aviraj.

    You've done well here to get all the elements in the design correct - i think with a few tweaks it could be perfect!

    • your box-shadow feels a little harsh in my view, a generator could be a really helpful tool to soften the shadow a little
    • I think your card is missing cursor: pointer;
    • i'd encourage you to review your accessibility report and fix the errors, they all seem to be to do with semantics and headings

    As the others have said you should look to conquer flexbox and grid, it'll make your life a lot easier instead of using absolute position and is a modern way to create responsive designs.

    Here are some really useful resources:

    • A Complete Guide to Flexbox - css tricks
    • Learn Flexbox for free - Scrimba
    • A Complete Guide to Grid - css tricks
    • Responsive Web Design - freeCodeCamp

    Good work and keep coding!

  • Zeynal Mardanli•180
    @Lshiroc
    Posted over 3 years ago

    Hi, I took a look your code and couldn't find CSS Flexbox and Grid. If you want to create responsive layouts (in this challange they don't require any responsive design if I'm not mistaken). And also it becomes so easy to create the ethereum and time part in the challange with flexbox. For example for this you should define the direction( row or column) and the you can separate them with just one line code. So, I advise you to learn flexbox and grid. But recent result is also good although you don't know flexbox and grid :). Have a good day

  • Web Wizard•5,690
    @rsrclab
    Posted over 3 years ago

    Hi, @avirajwalunj ~

    Congratulate on your solution to the challenge on FM platform. I have studied your work carefully and learned a lot from it. Especially I like the image overlay part you implemented.

    Here are some of the tips I like to provide. You can position the card using flex. align-items: center will make it vertically centered and justify-content: center will make it horizontally centered.

    https://www.frontendmentor.io/solutions/my-first-solution-on-chanllenge-V-4IzAivH

    Here is my solution to this challenge, and if it can help you even a bit, it would be happy to me.

    Cheers ~

  • Aviraj Walunj•80
    @avirajwalunj
    Posted over 3 years ago

    thank you very much for resources and advice.

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

Oops! 😬

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

Log in with GitHub