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

Colin's NFT Card Preview Project

Colin Meehan•40
@ucolinmee
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 found myself having to redo the style.css file, as I was simply reacting to how my card component looked at the time. For example, if I found my "card-footer" div was not aligned with the rest of the card, I would manually add margin until it aligned.

Then I realized once I changed my screen size, that the alignment would be all off yet again. I decided to upload my solution anyway so I could unlock the ability to view other solutions and seek inspiration on how they are able to align their content easily.

I am curious to find out what the best practice is for aligning content. For this project, I used flexbox and set my flex-direction to column, which helped quite a lot but I struggled slightly with some components, such as aligning the image to the center of the card.

Overall, this was a good challenge and I'm hoping that by learning from my peers, I will be able to style future challenges with less issues. On to the next challenge!

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • Ana Machado Amaral•310
    @MachadoA
    Posted over 1 year ago

    Hello, congratulations on the project! However, I suggest that:

    • Start with the mobile version; you'll find it much easier.
    • Add 'cursor: pointer' to all links and buttons consistently.
    • Include hover effects in the required places.

    Remember that after submission, you have the opportunity to see how others approached the same project. Take the chance to review and clarify any doubts you may have.

    See you soon!

    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 1st-party linked stylesheets, and styles within <style> tags.

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.

Oops! 😬

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

Log in with GitHub