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

HTML/CSS Beginner's First Attempt at a Challenge

Andy Ouyang•30
@ahouyang
A solution to the NFT preview card component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Thanks for anyone looking this over! I'm currently a software developer who works primarily in Java, but I have been learning front end web development in order to expand my skills/employability. I'm still learning the fundamentals so I recognize that my implementation of this challenge may be shaky.

What's the best practice way to apply CSS selectors? I found myself here using IDs sometimes, classes sometimes, and tag hierarchy sometimes, not totally sure when to use what. Are classes generally the preferred way? Or are classes only preferred when they're reusable? Some clarity on best practices here would be helpful!

I have many other questions about flexbox/why things were behaving a particular way but I think those are best answered by myself going through some solutions and trying them out.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Web Wizard•5,690
    @rsrclab
    Posted over 3 years ago

    Hi, @ahouyang ~

    Congratulate on your solution to the challenge on FM platform. I have studied your work carefully and learned a lot from it.

    Here are some of the tips I like to provide.

    1. I hope you to add transition on heading and creator name.
    2. Spacing, font-sizes don't match design. As a front-end developer, pixel-perfect and responsiveness is really important.
    3. For classing elements, I recommend using BEM structure. You can find about it on google easily.
    4. On smaller devices, things don't match design well.

    https://www.frontendmentor.io/solutions/my-first-solution-on-chanllenge-V-4IzAivH

    Here is my solution to this challenge, and if it can help you even a bit, it would be happy to me.

    Cheers ~

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