Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted over 1 year ago

NFT Preview Card

accessibility, lighthouse, bem
Mennatallah Hesham•1,470
@Mennatallah-Hisham
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, Frontend Mentor community. This is my solution for the NFT Preview Card challenge 👋

This is challenge 3 where I provide comprehensive guidance to fellow developers by adhering to industry best practices. By focusing on key areas such as

  • Semantic HTML
  • Clean web page structure
  • CSS enhancements
  • Accessibility
  • Performance Optimization

Today I want to share with you the advantages of using utility css class

  • utility class are css classes that applies a single rule or a very simple pattern.

Benefits

  1. dryness & consistency

    • help you reduce repetition and unintentional inconsistency in your styling

    • you can alter the value in one place instead

  2. file size

    • by reducing repetition, you reduce the file size which results in improving your page performance.

3- specificity

  • they also make it possible to creawte element specific overrides without writing high specificity varients.

Utility classes i used in this challenge



.clr-white{
   color:white;
}

.clr-cyan{
   color:var( --color-primary-cyan);

}
.fw-2{
   font-weight:var(--weight-2);
}
.fw-3{
   font-weight:var(--weight-3);
}
.ml-2{
   margin-left:0.2rem;
}
.my-2{
   margin-block:2rem;
}
.my-1{
   margin-block:1rem;
}

I aim to address common mistakes observed in the challenges submitted by other participants. Through this initiative, I hope to not only solve newbie-level projects but also share valuable insights and tips to aid in their learning journey. As a part of this initiative, I started a series Frontend Mentor - Learning from mistakes on Linkedin where I share common mistakes I found in newbies / junior challenges to assist all fellow newcomers in avoiding these pitfalls

  • mistake 1 : lang att
  • mistake 2 : inline css
  • when to use inline css
  • common css mistakes to avoid

Kindly note that I increased the font size and font weight for better readability

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on Mennatallah Hesham's solution.

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.