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

CSS Flexbox, HTML Div, HTML Basic, Max Width, Hoverstate, Positioning

Yu Dan•30
@SelfReflective
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 im Yu from Germany - aspiring Fullstack Web / App Developer. I´m still at the Beginning of my Journey but i have learned alot so far. This is my take on the NFT Card i felt like i did the challenge but in a very clunky way. I would LOVE to get some Feedback on my Code! I would aswell take a look at yours if you want :)

Thank you so much everyone!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Elir-Mahad•100
    @Elir-Mahad
    Posted over 3 years ago

    Hey Yu i looked over your code !

    It looks clean and not clunky at all.

    In your website: https://selfreflective.github.io/NFT-preview-card-component/

    There seems to be a horizontal and vertical scroll.

    This probably because of the height and width in your body.

    I played around with the css and i made some changes to body, .ntf-card, .boxshadow

    Implement the below changes to the css classes and let me know what you think.

    I identified the css properties that i removed by putting them under 'removed css below' comment.

    I identified the css properties that i added by putting them under 'added css below' comment.

    body {
      text-align: center;
      background-color: hsl(217, 54%, 11%);
      margin: 0;
      font-family: Outfit;
      
    /* removed css below  */
    /* width: 1440px; */
    /*  height: 900px; */
      
    }
    
    .ntf-card {
      border-radius: 10px;
      background-color: hsl(216, 50%, 16%);
      width: 340px;
    /* remove css below  */
    /* position: relative; */
    /* margin: 200px auto; */
      
    /* Added css below   */
      display:block;
      margin:auto;
      margin-top:2rem;
    }
    
    .boxshadow {
      display: flex;
      height: 300px;
      width: 300px;
      justify-content: center;
      align-items: center;
      position: absolute;
      border-radius: 11px;
      display: flex;
      justify-content: center;
      background-color: hsl(178, 100%, 50%);
      
    /* removed css below  */
    /* margin-bottom: 47px; */
    /* bottom: 234px; */
      
    }
    

    Also it would be useful, when you are writing out your code, to avoid using position relative and absolute unless its absolutely necessary.

    Try using flexbox and margins to move around the page.

    Thoughts ?

    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