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

3 column Preview Card Component using HTML and CSS

Brian•60
@briansegura15
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


Finally was brave enough to use a media query lol. Was wondering if anyone could check out the responsiveness and let me know if thats ok? Hopefully yes and ill be able to go back to my previous challenges and update them all with responsiveness. Thank you all!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Kent O'Sullivan•1,870
    @12Kentos
    Posted about 3 years ago

    Hey @briansegura15 Nice job on the media query! I checked over your code an notice something I thought I would point out. You have the following code.

    /* Box sizing rules */ *, *::before, *::after { box-sizing: border-box; }

    /* Remove default margin */ body, h1, h2, h3, h4, p, figure, blockquote, dl, dd { margin: 0; }

    Is there a specific reason you reset the margin the way you did?

    A similar way of doing it would simply be to include the margin: 0; inside of the * code block you have. Here's an example of what I'm talking about.

    *, *::before, *::after { box-sizing: border-box; margin: 0; }

    You could also include the padding in there as well, to do a complete and total reset.

    As for the media query, like I said congrats! I do have one suggestion though, I noticed once the query takes affect, it makes the entire component fit into the view screen, making everything small and hard to read. I would suggest allowing it to flow past the view screen, (vertically downwards that is) allowing everything to become a larger size. It's okay on a mobile phone for people to have to scroll to see the entire component, that's a natural thing on phones. Besides that everything is looking good!

    Hope that helps!

    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
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