Skip to content
Submitted about 2 months ago

blog-preview-card

Sebastian Gladysiak•40
@GladysiakSebastian
Preview site (opens in new tab)View code (opens in new tab)
This is a solution for...Blog preview card
  • HTML
  • CSS
1newbie

Design comparison

SolutionDesign

Solution retrospective

What challenges did you encounter, and how did you overcome them?

with Figma

Community feedback

  • Steven Stroud•11,890
    @StroudyPosted about 2 months ago

    Amazing job with this! You’re making fantastic progress. Here are some small tweaks that might take your solution to the next level…

    • Using a <main> tag inside the <body> of your HTML is a best practice because it clearly identifies the main content of your page. This helps with accessibility and improves how search engines understand your content.

    • Using font-display: swap in your @font-face rule improves performance by showing fallback text until the custom font loads, preventing a blank screen (flash of invisible text). The downside is a brief flash when the font switches, but it’s usually better than waiting for text to appear.

    • While px is useful for precise, fixed sizing, such as border-width, border-radius, inline-padding, and <img> sizes, it has limitations. Pixels don't scale well with user settings or adapt to different devices, which can negatively impact accessibility and responsiveness. For example, using px for font sizes can make text harder to read on some screens, Check this article why font-size must NEVER be in pixels. In contrast, relative units like rem and adjust based on the user’s preferences and device settings, making your design more flexible and accessible. Use px where exact sizing is needed, but prefer relative units for scalable layouts. If you want a deeper explanation watch this video by Kevin Powell CSS em and rem explained. Another great resource I found useful is this px to rem converter based on the default font-size of 16 pixel.

    • Using a full modern CSS reset is beneficial because it removes default browser styling, creating a consistent starting point for your design across all browsers. It helps avoid unexpected layout issues and makes your styles more predictable, ensuring a uniform appearance on different devices and platforms, check out this site for a Full modern reset

    You’re doing fantastic! I hope these tips help you as you continue your coding journey. Stay curious and keep experimenting—every challenge is an opportunity to learn. Have fun, and keep coding with confidence! 🌟

    Marked as helpful
    0
    Sebastian Gladysiak•40
    @GladysiakSebastianPosted about 1 month ago

    @Stroudy Amazing feedback ,thank you!

    1
    Steven Stroud•11,890
    @StroudyPosted about 1 month ago

    Hey @GladysiakSebastian, You got this! 💪

    0
  • Roberto Keppler•130
    @rkeppler42Posted about 2 months ago

    Hey, Sebastian! Great job!!! It is a pretty close solution.

    I would only include a border in the card and a shadow too - similar to the original design.

    HTML I would use more semantic tags (main, for example). Don't rely too much on divs alone. You can use them but, what part of the site are they in? It is good practice for your future you and others who will see and work with your code. It is important too because of accessibility and SEO.

    On the CSS front I think that someone with more experience could help you with responsive design.

    Great work! Cheers!

    Marked as helpful
    0

Please log in to post a comment

Log in with GitHub

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