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

Responsive 3 Columns Layout Done With Flex

KoliaK•160
@KoliaK
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


I guess I'm having problems setting width/height/max-width/max-height and deciding wether I should use vh or % units for those. What do you usually do to make responsiveness keeping everything in ratio?

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Alper•1,090
    @adonmez04
    Posted almost 2 years ago

    Hi, @KoliaK.

    That's a good solution. Keep coding.

    I know that units of measurement can be a bit confusing at first. There are so many types of units and they all work differently. I prefer to use px and rem first to keep everything simple. And you don't need to give any height values for your elements.

    In fact, elements take their width and height values from their content. They can be font-size, line-height, font-weight and padding&margin values etc. You can assign a max-width value for the container element and its child elements will grow and shrink depending on this value. Because the HTML itself is responsive. We can break its function if we give some width and height values from CSS.

    This concept might be difficult at first glance. But step by step, everything will make sense. I highly recommend Kevin Powell's course. I have learned a lot from this, it's free and easy to follow.

    https://courses.kevinpowell.co/conquering-responsive-layouts

    Unfortunately, there is no magic way to learn everything at once. You need to spend some time in the course to understand the fundamentals of the responsive design. However, it will be worth it.

    I hope this will help you. Keep coding and have a wonderful day.

    Marked as helpful
  • Alper•1,090
    @adonmez04
    Posted almost 2 years ago

    And maybe this resource can help you to use devtools for mobile devices more efficiently: https://developer.chrome.com/docs/devtools/device-mode/

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