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

3 Column preview Card - HTML and CSS

Angus Turnbull•70
@echoturnbull
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 all,

I had a few issues with this one. For some reason I could not figure out how to make the columns contain all my information as they are resized.

I need some advice on if I am displaying things correctly. How I should position these thing within the divs to make them stay in position and how to maintain the aspect ratio of the entire card while the browser is being resized.

Anyone that takes the time to look at and respond, thank you very much, I am extremly gratefull.

Angus

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • Caleb Sim•410
    @CodeLamp168
    Posted over 2 years ago

    Container does not have a width given that's why the text is moving. However it does not center if you do.

    A tip: When you are making similar designs for each card, give them all the same class name. You can implement more than just one class to each. For class "item1" "item2" "item3". Instead write: "card item1" "card item2" "card item3" Now card and item are seperate classes for the element and can be good for organizing in css.

    So I use the class "card" for setting the width, height, and the padding for each card. You can set height to auto/height:auto and work through using margins for the text or just set a determined height. Usually recommend height:auto Then I use "item1" to design that specific card's color and image.

    Don't text-align:center on body. I usually do it on specific areas. But you can set the font-size and font-family there. check the style-guide thats given.

    Also its good practice to start designing by mobile first so that it can be responsive. Simply remove the display:flex on container and you have atleast a template for what the mobile design would be like. Then use ex: @media (min-width: 50em) { .container { display:flex; } for the desktop version. }

    This means when the screen hits 800px, the container will become display:flex. (You wont need to repeat any code just need to position the elements to row)

    You can look at my solution's html and css. However there are simpler solutions on github and they really do help make you understand the structure if you go through them.

    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