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

just plain html and css

jake•140
@jakewebd
A solution to the NFT preview card component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


constructive criticism is appreciated.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • riverCodes•300
    @riverCodes
    Posted about 3 years ago

    Hi, congratulations on the solution. Here are a few things you can improve on, -

    • For the HTML and Accessibility issues, put alt attributes on your images and icons. Change your div.main-container to main.main-container (<main class="main-container>). Whenever you use a section, it needs to have one heading element inside it, and the whole page needs to have at least one <h1> tag.

    • I noticed your card is not centered on the page. For this, i recommend this resource. It's a great standard way that you can use to center a lot of the components in the frontend mentor challenges. Link: https://every-layout.dev/layouts/cover/. In short, you want to put this CSS in your body tag: min-height: 100vh, display: flex; flex-direction: column; align-items: center; justify-content: center; This will force your <body> tag to cover 100% of the viewport height (by default, element heights usually depend on inner content height). and then use flexbox to apply centering properties.

    • additionally, you can apply this code to your <main> tag margin-block: auto; and to the <footer> margin-block-start: 1rem this will force your footer tag to always have 1rem of space from the main tag and will keep the main tag centered vertically.

    • Lastly, your design seems to be quite smaller than the reference. I suggest you to use rem units instead (relative to the font-size mentioned in the style-guide.md) and bump up the sizes of everything. Small text is more for printing, on screens this affects readability.

    Good job though :D Keep on learning!

    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