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

Preview Card – Responsive Design with HTML & CSS

bem, pure-css
antonioReynaldo•80
@antonioReynaldo
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 creating a fully responsive solution using only HTML and CSS without needing JavaScript. Using media queries and design techniques like Flexbox and Grid really allowed me to make the layout flexible and easy to adapt. Next time, I could further optimize the image structure or add subtle animations to improve interactivity.

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

One of the biggest challenges was making sure the card looked good on both small and large screens. To overcome this, I focused on a mobile-first approach, adjusting sizes and alignments as I scaled the design. I also had to tweak margins and spacing to prevent elements from overflowing on smaller screens.

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

’d love feedback on how I could optimize the performance of images, as image size is important in a responsive design. Additionally, I’d like to know if there are ways to make the design more accessible or improve the semantic structure of the HTML.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Carlos Gómez•110
    @CarlosLDC
    Posted 6 months ago
    • Lo único que no me gusta es que la escala de tu solución es diferente. Pero eso no es muy importante.
    • Yo también pensé usar flex en la parte del usuario, pero me terminé decantando por inline-block. ¿Puede que flex sea una solución más elegante? Creo que sí.
    • Me doy cuenta de que también usas código DRY (cuando definiste el margen de base). Creo que esta herramienta es muy útil para los tipos y tamaños de fuente.
    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
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