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

NFT preview challenge using HTML and CSS

Nitesh Singh•40
@niteshh-s
A solution to the NFT preview card component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


I am new to Web development. I Made this website using beginner level HTML and CSS. No bootstrap used. It appears perfect on desktop screen. I would really appreciate if anyone can suggest me how can i make this website completely responsive.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Naveen Gumaste•10,420
    @NaveenGumaste
    Posted over 3 years ago

    Hello Nitesh Singh ! Congo 👏 on completing this challenge

    Let's look at some of your issues, shall we:

    • Check my article on accessibility issues

    • Always use h1 first and then h2, h3 and so on

    • Headings should only increase by one use h1 first then h2 etc..

    • Warp your card content around the main tag Ex: 👇

    <body>
    <main class="container">
    *all you content here*
    </main>
    </body>
    

    If you use vs code the check this article

    happy Coding😀

    Marked as helpful
  • Nitesh Singh•40
    @niteshh-s
    Posted over 3 years ago

    Thank you so much for your valuable feedback. I will take your words into consideration. I am new to web development and not yet familiar with many tags. Hopefully I'll reach your level soon.

  • Shashree Samuel•8,860
    @shashreesamuel
    Posted over 3 years ago

    Hey niteshh-s, good job completing this challenge. Keep up the good work

    Your solution looks great however I think the card needs to be scaled up a bit. You can do this using transform: scale(). The user avatar and author should match the design, it is not supposed to be replaced. Lastly the image should be a bit wider to match the design.

    In terms of your accessibility issues simply wrap all your content between <main> tags to get rid of all issues

    In addition I recommend that you start using html semantic tags since it will greatly improve your code.

    Read more on it here

    https://www.w3schools.com/html/html5_semantic_elements.asp

    You can make this website completely responsive using css media-queries. I recommend reading up on it since they utilize breakpoints in order to adapt to various devices

    I hope this helps

    Cheers Happy coding 👍

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