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

Card Component with HTML and CSS

Ukan•20
@ukanlei
A solution to the NFT preview card component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


This simple card component was a lot more challenging than it looked. One thing I struggled with the most in this project was organizing my stylesheet. I find myself going back and forth between my codes and mock-ups, thinking I have finished only to realize I have missed some essential styling components. Ultimately, this disorganization has affected my workflow and quality of work.

Questions:

  1. What are the standards or best practices when it comes to organizing CSS and making it more manageable?
  2. How can I reduce repetition in my CSS?
Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Mary Njoroge•150
    @Maryahcee
    Posted about 3 years ago

    To avoid repetition in CSS I use class with same name when there are several elements that need same styling design. Also breakdown sections if it's Navbar section check to see what elements have similar design and give them same class name.

    Finish designing one section at a time it makes the work easier and you won't have to keep repeating your self. Cheers! Keep coding!

  • Mary Njoroge•150
    @Maryahcee
    Posted about 3 years ago

    Hi the card looks good. At first someone struggles with finding the best working flow. However I have some tips that have helped me become organized while working on my projects. First look and analyize the design and make a sketch of how I will approach the design. Second write down all sections (eg. Navbar, Main, footer.) in the design and what I will use (eg flex or grid) to make them. If you do this routine in your first projects you will notice that in the future you won't necessarily have to do it it comes naturally with more practice. I hope this helps. Happy coding!

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