Skip to content
  • Unlock Pro
  • Log in with GitHub
Profile
OverviewSolutions
9
Comments
1

gowthamss

@gowthamssIndia185 points

I am a UI developer with a year of experience. I love front-end development.

I’m currently learning...

React, Cloud Computing, Styled Components.

Latest solutions

  • URL shortening API landing page using React.


    gowthamss•185
    Submitted about 4 years ago

    1 comment
  • Social Media Dashboard using HTML, CSS, and JS.


    gowthamss•185
    Submitted about 4 years ago

    0 comments
  • Calculator using JS, HTML and CSS.


    gowthamss•185
    Submitted about 4 years ago

    1 comment
  • 3column-preview-card-component using HTML and CSS


    gowthamss•185
    Submitted over 4 years ago

    1 comment
  • Responsive stats preview component using HTML and CSS


    gowthamss•185
    Submitted over 4 years ago

    0 comments
  • Profile card using HTML and CSS


    gowthamss•185
    Submitted over 4 years ago

    0 comments
View more solutions

Latest comments

  • Hugh•55
    @hugh128
    Submitted about 4 years ago

    Stats preview card component solution using CSS Flexbox.

    2
    gowthamss•185
    @gowthamss
    Posted about 4 years ago

    Hi, I have gone through your solution. I noticed that your '.card_texts' and '.card_picture' are the two children inside the '.card'. If you set width to child elements by percentage, they will always be aligned with respect to their parent container.

    1. In mobile and tablet resolutions, if you see image and the content('.card_texts') are stacked on each other. So, they are occupying the full width of the '.card' container(parent). In this case you set whatever width you want to set to your '.card_texts' div and it will be aligned according to it.

    2. But in the case of desktop, your '.card_picture' is taking a width of 540px(inspect and see) in all the resolutions after 1019px. So, now your '.card_texts' is left with the width that is '.card' container width - '.card_picture' width. So, it can only grow and shrink in that particular width only. Note: Try applying the width to '.card_texts'(you can apply from say 10% and increase to see where it stops getting applied) in the dev tools of chrome.

    As I noticed, in 1366px resolution, the '.card_texts' can grow up to 50%. And this percentage will be reduced as you reduce the screen resolution. Ex: in 1020px resolution, it takes up to 40%.

    Probable Solution: 1.In order to avoid this behavior and have both the '.card_texts' and '.card_picture' have equal size in all the desktop resolutions, try applying width: 50% to both the containers. So they take the equal size in all desktop resolutions. 2. Or you can apply CSS grid to your '.card' container having two columns taking '1fr 1fr'. By applying this they will always be divided into two parts of the container and take the equal size.

    Let me know what you think and if my explanation is difficult to understand, please add a comment. I'll try to explain again.

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

Beta Member

This badge is a shoutout to the early members of our community. They've been around since the early days, putting up with (and reporting!) bugs and adjusting to big UX overhauls!

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

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

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

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

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

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

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

Oops! 😬

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

Log in with GitHub