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

Responsive NTF card component using plain HTML and CSS

Andrés Sanabria•20
@jandrev
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 there! I got in quite a lot of trouble determining when I should use an ID and when I should use a class. How can I optimize my use of IDs and classes? Another thing that bugged me is that I had to nest three divs to create the shadow of the main card. How can I improve the creation of these shadows? I tried using box-shadow, but I could not control the width and height of the shadow.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Iole•80
    @d4lbit
    Posted over 3 years ago

    Hi! Usually ids are used only one element and classes on multiple elements :) Also remember that when applying CSS ids have priority over classes. As for the shadow, you can just apply it on the outer parent div of the card. From my newbie point of view I found your HTML a bit 'too messy': you could have done your card with less divs. But it's a good try anyway! If you have troubles with CSS I suggest you visiting CSS Tricks, it may help you :)

    Keep going, it's going to be easier!

  • Agata Liberska•4,075
    @AgataLiberska
    Posted over 3 years ago

    Hi @jandrev! Nice work here :)

    • In general, it's best to stick to classes when styling. Id's have a higher specificity than classes, which can have some unexpected results and is trickier to maintain (but they do come in handy for working on very large sites when you want to make sure you don't change something accidentally).
    • For shadows, definitely use box-shadow. You can control the height and width with offset values - and keep in mind that those nice soft shadows you see on websites are most likely multiple shadows on top of each other. Check out this website for some great examples
    • Additionally, it would be good to have some more semantic html tags here - definitely a <main> (that's the issue that is showing up in the report), you could also use <article> for the card itself.
    • I can see you set up the height of the card element - it's really unnecessary here - it's a lot better to control the width with specific values and then let the content decide the height.
    • Make sure the alt text for your images is meaningful - describe what you can see in the image :)

    Hope this helps! :)

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