Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted over 1 year ago

Responsive blog preview card using Grid

Reno G•60
@pamplito
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 to have completed this challenge and, above all, to have kept looking for solutions until I finally achieved what I wanted to provide.

This chalmlenge made me learn and progress and I'm sure I'll begin the next one with more confidence.

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

I had trouble with the image's responsiveness. I wanted the height to be fixed but the sides to be responsive without distorting the image.

I finally managed to find a solution with OBJECT-FIT, which allowed me to crop the image in a fluid way.

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

As I've only recently started to learn programming on the web on my own, I'd love to get feedback and advice from more experienced people to help me progress more quickly.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • D. Jaime Blockton•180
    @digigrrl525
    Posted over 1 year ago

    I think this is bang on. Awesome job!

    Marked as helpful
  • rezanahi•60
    @rezanahi
    Posted over 1 year ago

    Great! In my opinion, it would be even better if you also add hover effects.

    Marked as helpful
  • P
    Øystein Håberg•13,280
    @Islandstone89
    Posted over 1 year ago

    Hi Reno, great job.

    You have included:

    • The main landmark
    • A proper CSS Reset
    • Custom Properties
    • font-size in rem instead of px

    Well done!

    Here are some suggestions to improve your code even further. I hope you find them helpful :)

    HTML:

    • Never have text in divs alone. "Learning" is a <p>, and I don't think it needs to be wrapped in a <div>.

    • The publish date is a good opportunity to use the <time> element:<p>Published <time datetime="2023-12-21">21 Dec 2023</time></p>.

    • Don't use words like "photo" or "image" in the alt text. A more descriptive sentence would be "Headshot of Gary Hooper".

    CSS:

    • The main shouldn't have any properties, move them to .container.

    • max-width on the card should be in rem.

    • Remove all heights in px.

    • Media queries should also be in rem.

    Marked as helpful

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

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

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub