Social profile links

@damigand,

To address your points:

1. I understand that the main tag is typically used for the main content, which, in this case, is a card. However, I wrote it this way to allow for the possibility of having multiple cards in the main section. This approach will make reusability of styles if we need to add more than one card.

2. I generally follow a component-based perspective in my projects, which helps in maintaining a modular and scalable codebase.

3. There is a note in the example readme.md file regarding CSS for smaller screens: "Ensure content is responsive and meets WCAG requirements by testing the full range of screen sizes from 320px to large screens." This is because some users still have smaller phone screens. I consistently use a mobile-first approach in all of my projects to ensure responsiveness and accessibility.

Thank you for taking the time to review my work.

@RobertsPeirags

I can understand the first two points, they're pretty understandable. About the third point though, the solution I suggested (with very little testing on your live site) makes your card accessible even down to 220px of width (with the slight adjustment of text-wrap: wrap on the bio), and saves you time in the rest of the queries that you have established for other screen widths. Obviously this is my subjective point of view, neither of us are wrong (or so I'd like to think, sometimes I am wrong :P)

@damigand While you can make screen size lover than 320 pixels... 320px is generally considered the minimum width for responsive web design, as it covers most modern smartphones.

But again, I might be wrong on this.

@RobertsPeirags Yeah, there's no objective way to determine the right way of doing things. Hey, as long as it works! Love to see your work!

Cheers!