Not Found
Not Found
Not Found
Not Found
Not Found
Not Found
Not Found
Not Found
Not Found
Not Found
Not Found
Not Found
Not Found
Not Found
Not Found
Not Found
Not Found
Not Found
Not Found
Not Found

Submitted

3-column preview card component solution

P

@Jacoappolinario

Desktop design screenshot for the 3-column preview card component coding challenge

This is a solution for...

  • HTML
  • CSS
1newbie
View challenge

Design comparison


SolutionDesign

Community feedback

P

@newtothis90

Posted

IN THIS INSTANCE, there's no need to give your <img> a class name at all since you are already using img{}. Giving it a class isn't wrong at all, but a little less code with not giving them a class.

Hope this helps somewhat. If you have a reason for giving them a class of .image, please explain. I would love to hear your opinion.

Regardless, GREAT JOB!

0

P

@Jacoappolinario

Posted

@newtothis90 For the sake of visual organization of my code I prefer to leave it like this. I could call the img {}, but visually it wouldn't be so cool, so I'd rather create another new class name haha. But it does make sense what you said, in this case it's more about personal taste and structure, but thanks for the feedback.

1

Please log in to post a comment

Log in with GitHub
Discord logo

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