Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 3 months ago

Responsive Blog Card with HTML & CSS

Sreejith c s•20
@sreejithcs007
A solution to the Blog preview card challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


What are you most proud of, and what would you do differently next time?

I'm proud of how far I’ve come from my previous project. In this blog card design, I was able to implement a clean layout using flexbox, apply good use of typography with Google Fonts, and create a component that actually looks like something you'd find on a real website. Compared to my earlier QR code project, this one feels more polished, detailed, and functional. I’m also proud that I managed to keep the styling clean and consistent — it’s visually appealing without being overcomplicated.

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

One of the main challenges I faced was balancing spacing and typography. It was tricky to make sure everything had enough breathing room without making the card feel too stretched or empty.

What specific areas of your project would you like help with?

I'd love help making the blog card more responsive — especially tips on using media queries or CSS Grid to adapt the layout for smaller devices without breaking the design.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    M Kerr•2,130
    @mkerr-github
    Posted 3 months ago

    Looks great, well done !

    "I'd love help making the blog card more responsive — especially tips on using media queries"

    Basically, you can use media queries, where you can specify in the CSS that certain properties and sizes should change once the pixel size of the screen reaches a certain size.

    Here is a nice short explanation as well on W3 schools:

    https://www.w3schools.com/css/css_rwd_mediaqueries.asp

    For responsive purposes the convention is to convert these measurements to "rem", to do so divide them by 16 (as the base rem is 16px).

    Then use max-width to set the large size and min-width to set the small size.

    The convention is to use rem and sometimes em, instead of pixels for most items, as they are more responsive. pixels can be used for small elements like icons and buttons where you do not want the size to change even on small screens.

    More details here: https://austingil.com/px-or-rem-in-css/#:~:text=Pixels%20are%20an%20absolute%20unit,the%20equivalent%20of%2024%20pixels.

    If you found anything in this comment helpful, please remember to click the "mark as helpful" button. Thank you!

    Keep up the good work, and keep going! 👋

  • Gabriel Rodriguez Perez•160
    @glrodriperez98
    Posted 3 months ago

    Hey! Great job on this project, your progress is really clear, and it's awesome to hear how you're building on your previous work like all of us. The way you described your improvement from the QR code project to this one shows solid growth in both layout and design thinking.

    Your use of flexbox and Google Fonts gives the card a clean, modern feel.

    The attention to typography and visual balance stands out, it's not easy to keep things looking polished and functional, and you pulled that off nicely.

    A couple of suggestions:

    • Since you're thinking about responsiveness, you're on the right track! Starting small with media queries to adjust padding, font sizes, or even switch to a CSS Grid layout at certain breakpoints could really level up the flexibility of your design.

    • You might also want to explore using relative units like em, rem, or % instead of fixed px values in some places, this helps layouts scale more naturally across screen sizes. You used % once or twice but could be worth exploring more!

    The one other thing I noticed is that your border shadow is a little bit thicker around the top and left than it is in the design. This is something I struggled with as well! If you get any additional feedback regarding that part I'd love to hear it.

    All in all it was a great solution and you're definitely on your way to becoming a developer!

    Kind regards, G

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 all CSS, SCSS and Less files in your repository.

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.

How does the JavaScript validation report work?

When a solution is submitted, we use eslint to run an automated check on the JavaScript code.

The report picks out common JavaScript issues such as not using semicolons and using var instead of let or const, among others.

The report will audit all JS and JSX files in your repository. We currently do not support Typescript or other frontend frameworks.

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