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

Blog preview card

tailwind-css
P
jeffgrahamcodes•260
@jeffgrahamcodes
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 most proud of how well I was able to structure and style the layout, ensuring it looks clean and consistent across different screen sizes. The use of semantic HTML and well-organized CSS with variables for colors, spacing, and typography made the code more readable and maintainable. I’m particularly happy with how the card's design matches the original Figma design and maintains visual balance on both desktop and mobile devices.

If I were to do something differently next time, I’d pay closer attention to edge cases in responsiveness, particularly for very small screen sizes. I noticed some styling issues, like the border-radius on images, that only became apparent during testing on narrower viewports. Moving forward, I’d include more rigorous mobile testing earlier in the process and refine my approach to handling image scaling and overflow within constrained containers.

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

One of the biggest challenges I encountered was ensuring the design remained consistent across different screen sizes, particularly on smaller devices with widths under 375px. The issue with the border-radius on the blog image disappearing at smaller breakpoints was especially tricky to troubleshoot. Initially, it wasn’t clear whether the problem stemmed from the image itself, its container, or a combination of both.

To overcome this, I revisited my CSS, focusing on properties like overflow: hidden and ensuring both the container and the image had explicitly defined border-radius values. I also utilized object-fit: cover to ensure the image scaled correctly while respecting its rounded corners. Testing across multiple devices and refining the mobile-specific styles in my media queries ultimately resolved the issue. This process reinforced the importance of thorough responsiveness testing and double-checking how parent and child elements interact at different breakpoints.

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

I’d appreciate feedback on how I handled responsiveness, particularly for very small screen sizes (under 375px). While I addressed the issue with the image’s border-radius, I’m curious if there are more efficient or scalable ways to handle image scaling and overflow in constrained containers. Additionally, I’d like guidance on improving accessibility, especially in terms of ARIA roles, and focus states for interactive elements. Lastly, if there are any best practices I might have missed for structuring CSS with variables and media queries to make the code even cleaner and more maintainable, I’d love to hear those suggestions.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Macdonald Nkhata•90
    @MacNkhata
    Posted 7 months ago

    There is nothing to add. keep doing what you are doing

    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