Blog Preview Card Component Using HTML and CSS

@grace-snow Thanks for suggestions. i have refactored based on few of your suggestions. Please see if the overflow still exist on your mobile

@karthikganesanTR sorry, this still has problems.

You've misunderstood and over-complicated a few bits actually:

• don't change aria-level on the heading! If this was used on a page listing blogs it would result in loads of h1s on a page and be hard to understand the content.
• the alt on the avatar needs to be unique to that image. Same issue in a way... "Avatar" is not descriptive of an image yet every blog card would have that alt description.
• height 100vh is causing the whole card to get cut off at the top in some screen sizes/orientations. Use min-height so elements are not limited to the height of the viewport.
• this challenge should not have any media query, you can delete all of that. The card simply needs a max width in rem so it can shrink narrower when it needs to. I say to use rem there so the layout scales correctly for all users, including those with a different default text size. (Also note for future, if using media queries, you'd place the larger screen style changes in there and keep mobile styles as the default, and you.wouod need to define media queries in rem or em not px — I've written about this on FEDmentor.dev if you want to take a look)

Some minor css suggestions too

• it's better for performance to link fonts in the html head instead of css imports.
• try to get into the habit of including a full modern css reset at the start of the styles in every project. It will make your life easier. Andy Bell or Josh Comeau both have good ones you can look up and use.

@grace-snow.

• Thanks for pointing it out, accessibility report says page should have h1 element. so, tried to make h2 it as h1 to clearing warning on the report
• Regarding min-height vs height, m not clear on min-height: 100vh not cutting on top (but actually touching the top) but height: 100vh cutting on top. can provide some reference on this topic
• Regarding not to use media queries, i have replaced with max-width as rem. How to make sure very developing closer to the design or we can tradeoff on something in the design. (both mobile and desktop)
• In my laptop, card is touching the edges of screen at certain screen sizes - is this due to content and spacing. To fix, i have added margin: 1.5rem in the container, is this correct

@karthikganesanTR

• the warning is only because an automated scan assumes this is a full Web page, not a single component. It does not need a h1.
• you can replicate the issue on small phones in landscape mode. It's a key difference - height is a fixed value, that's like setting a limit "it must be this exact height". Min-height is saying "make it at least this height", this allowing the element to be taller if and when needed to fit the content in.
• I don't understand the question about media queries... Are you saying the figma design has different font sizes on mobile so is needed for that?
• it's fine to add margin to components but unlikely to be the correct approach for this on a card, because it's often placed in a grid where gap would be used on a real page. I would choose to add some padding on a wrapping element (like the body or main) in this kind of component demo instead.

@grace-snow

• Yes. figma design has different font-sizes on mobile version.

@karthikganesanTR man, that's annoying and unnecessary! 😂

I'm that case, it's fine to have a media query. Or use clamped font sizes like those generated by Utopia

@totorocod Thanks for feedback. how to be make sure we are following same margin, padding , width etc given in design files. I mean making sure if we are using relative units like percentage or view port, we can have markup as same in design files since alignment, spacing are given in pixels.

@karthikganesanTR don't use percentages or viewport units. Components like this should only have a max width in rem. That will allow it to grow only up until that max width, but will allow it to shrink narrower on smaller screens. There's no need for any media query or other adjustments for different screen sizes on a card like this.

For paddings and margins you can use rem, em or px.

• rem when you want the value to change consistently along with the users chosen text size. So if they have a default size of 32px for font in their browser (200% of the default 16px) whatever you set in rem would be double the size.
• em is rarely needed. It is for when you want a value to scale with the current or parent element's font size. For example, padding in a button, or margin top / gap within a block of prose content like a blog so the space above headings is a little larger than the spacing above paragraphs (because headings have a larger font size).
• use px when you want a value to stay fixed and never change no matter what user settings or screen size used.