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

CSS flexbox responsive card component

accessibility
Elizabeth Sotomayor•230
@elizabethrsotomayor
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 had some trouble with getting the image the right size initially. I set it to several different values/percentages but ended up leaving it as-is since it looked okay when it was inside of the card container. The <hr> gave me some trouble as I couldn't get it to look the same as the design mock up. When I gave it a margin of 1rem on top and bottom, the <hr> completely disappeared but when I made the values smaller it seemed to fix the issue. Thank you for any feedback!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Mohammed Fakih•1,590
    @javascriptor1
    Posted almost 2 years ago

    Hi Elizabeth Sotomayor ,

    Nice work. There is an active state design which I think you forgot to do. its acheive when you hover over he image , h1 tag and creator name in the design.

    Keep coding 👍

    Marked as helpful
  • Salah Shadoud•240
    @SalahShadoud
    Posted about 2 years ago

    hey there! nice work

    • you can use the gap property to set a fixed space between card childs instead of setting margin to each child element, i think it is a better way of spacing elements in a flexbox container and this way u can control the spacing from one place instead of dealing with multiple spacing properties.

    Happy Coding <3

    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

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub