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

Responsive blog preview card with HTML & CSS

bem
Renita M•40
@renitam
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 not sure. This project along with the QR Code and Social links profile are pretty repetitive. I got it done in under an hour.

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

Not many challenges to report. Code was smooth. I needed to specifically define the tag margins to match the figma.

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

Let me know if I missed anything important!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • J. Dheeraj•50
    @dheeraj78
    Posted about 2 months ago

    I should agree that i really like the way the CSS has been written i mean it really is formatted and follows the standard naming convention and declaration. Which I'm still trying to learn. The problem that i saw was the page not being responsive in smaller screens it would be better to resize the main image and also change the screen height so the main card could be in middle or set some margin in top and bottom.

  • P
    Michael•180
    @Networksentinel
    Posted about 2 months ago

    Hi Retina, your solution looks great — I love the mobile-first approach! 😊

    I reviewed your code and wanted to mention a few things I noticed:

    • On mobile screens, when the phone is flipped, the <footer> gets pushed a bit too close to the card.
    • In the Design comparison view, the desktop layout appears smaller than the design specs.
    • The card isn’t fully centered vertically relative to the screen — the <footer> takes up some of the viewport height, which affects the alignment.

    I took the opportunity to clone your repo and experiment a bit. Here’s what I changed:

    • Added some top padding to the <footer>.
    • Centered the card vertically with a few small CSS tweaks.
    • Reorganized index.html and styles.css slightly to reduce repetition and improve clarity.

    I didn’t adjust the sizing yet, since that would take more tweaking. But for sizing, I used clamp() in my version of the challenge because I wanted to complete it without using media queries — and clamp() worked perfectly for that!

    If you're interested, I’d be happy to open a pull request so you can check out the changes — and we can also talk more about how I used clamp() for responsive sizing 🙂

    Whether you respond or not, thank you — your solution gave me the chance to clone a repo and work with someone else’s code for the first time!

    Keep up the awesome work!

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