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

HTML, CSS, Flex, media query

Charissa Ramirez•30
@chawissa
A solution to the 3-column preview card component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Hi! It took me longer than I thought. It took me a while to figure out why justify-content wasn't working as expected. It finally worked when I put the height and the width on .card instead of on .container.

Please give feedback on the quality of my codes and the class names and whatever else you can think. It tried to make it as clean as I can and use the DRY method.

Thanks.

Charissa

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Charissa Ramirez•30
    @chawissa
    Posted about 4 years ago

    Thanks Janne for calling me out on the pseudo classes and media queries. I actually avoided those because I'm not comfortable yet. :) I'll do better and try harder.

    Regarding line 25, I remember seeing the border when I was trying to get it centered so I just put it there.

  • Janne Tielinen•90
    @Tielinen
    Posted about 4 years ago

    Good work Charissa,

    "It took me longer than I thought." That happen to me too, a much longer on my first solution. On second one, things got easier/faster.

    To my beginner eye your code looks great, well organized, easy to read effective code.

    Few minor things got my attention, In style.css; line 25, do you need 'border: none;' declaration?

    I would consider pseudo classes first- and last-of-type to cards border radius declarations, so you can stack more cards later if you need to. And I think code is a little bit more readable this way. ''' .card:first-of-type { border-radius: 1rem 0 0 1rem; } .card:last-of-type { border-radius: 0 1rem 1rem 0; } '''

    I would make sure that the layout looks good in middle screen sizes, like tablets. Now on 768PX view-port "Learn more" buttons come out of their containers. It might help to just set break-point 768 PX and then make sure that the mobile layout looks good until break-point.

    Like mentioned before, good work, in any case, and especially for the first solution.

    Best wishes Janne

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

Oops! 😬

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

Log in with GitHub