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

Preview Card Component with CSS

NicholasChristopherBlake•130
@NicholasChristopherBlake
A solution to the Product preview card component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Here' my solution for this challenge. Please suggest what could be done in a better way.

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • Vicktor•920
    @Victor-Nyagudi
    Posted over 2 years ago

    Good job on this one.

    I've noticed that you used an id attribute in many tags in your HTML for styling purposes. While this isn't bad for a simple solution like this one, it's good practice to use classes instead.

    An id has to be unique, so if you wanted to style, let's say, 10 things the same way, you'd end up having to create a unique id for each of them and remember to style each one correctly. Furthermore, you'd need to remember each id name which creates unnecessary extra work for you.

    Here's an example of HTML where id is used to style many things the same way. Avoid this!

    <ul id="articles">
         <li id="first-article"> 
              <h2 id="first-heading"> My Trip To Malaysia</h2>
    
              <p id="first-article-body"> Lorem ipsum dolor...</p>
         </li>
    
         <li id="second-article"> 
              <h2 id="second-heading"> Backpacking in Colorado</h2>
    
              <p id="second-article-body"> Lorem ipsum dolor...</p>
         </li>
    
         <li id="third-article"> 
              <h2 id="third-heading"> Why I Don't Like Restaurant Food</h2>
    
              <p id="third-article-body"> Lorem ipsum dolor...</p>
         </li>
    
         <li id="fourth-article"> 
              <h2 id="fourth-heading"> 5 Ways To Save During Trips</h2>
    
              <p id="fourth-article-body"> Lorem ipsum dolor...</p>
         </li>
    </ul>
    

    Here's what some of the CSS might look like. This can get very messy very quickly, especially in bigger projects.

    #first-article, 
    #second-article,
    #third-article,
    #fourth-article {
         color: black;
         border-radius: 5px;
         background-color: grey;
    }
    
    #first-heading,
    #second-heading,
    #third-heading,
    #fourth-heading {
         font-size: 2rem;
         font-weight: 600;
         color: purple;
    }
    

    With a class, you just need to make one class and apply it to the elements that need to be styled the same way.

    Here's HTML using a class.

    <ul class="articles">
         <li class="article"> 
              <h2 class="article-heading"> My Trip To Malaysia</h2>
    
              <p class="article-paragraph"> Lorem ipsum dolor...</p>
         </li>
    
        <li class="article"> 
              <h2 class="article-heading"> Backpacking in Colorado</h2>
    
              <p class="article-paragraph"> Lorem ipsum dolor...</p>
         </li>
    
         <li class="article"> 
              <h2 class="article-heading"> Why I Don't Like Restaurant Food</h2>
    
              <p class="article-paragraph"> Lorem ipsum dolor...</p>
         </li>
    
         <li class="article"> 
              <h2 class="article-heading"> 5 Ways To Save Money On A Trip</h2>
    
              <p class="article-paragraph"> Lorem ipsum dolor...</p>
         </li>
    </ul>
    

    Now in the CSS, you'll just need to style the .article class or .article-heading or whatever else you want to style, and it applies to every element that has that class.

    // Anything with an "article-heading" class will have this styling applied
    
    .article-heading {
         font-size: 2rem;
         font-weight: 500;
         color: purple;
    }
    
    // Anything with an "article-paragraph" class will have this styling applied
    
    article-paragraph {
         font-size: 1.125rem;
         font-weight: 400;
         color: black;
    }
    

    Try it in your code, and see the results for yourself.

    Here's an article on CSS selectors that will help you understand this topic more.

    Hope this helps.

    All the best with future solutions.

    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

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