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

Solution to the "Blog Preview Card Component"-Project using HTML/CSS

Dias•140
@adambeckercodes
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? What I’m Most Proud Of

I’m most proud of how clean and organized my code turned out, especially with the use of CSS variables and Flexbox for layout. It feels great knowing the design is not only responsive but also accessible, with ARIA labels and focus-visible styles for better keyboard navigation. Adding the skip link was a small but meaningful touch that enhances usability.

I’m also really happy with the modern, polished look of the card component. The hover effects and the box-shadow give it a nice, interactive feel without being overwhelming.


What I Would Do Differently Next Time

I’d explore adding subtle animations or transitions to make interactions even smoother.

Additionally, I’d like to test the project more thoroughly with screen readers and accessibility tools to ensure it works seamlessly for all users.

What challenges did you encounter, and how did you overcome them? Challenges I Encountered

One of the main challenges I faced was ensuring the card layout stayed responsive and visually appealing across different screen sizes. Balancing the use of min-width and max-width properties while ensuring proper padding and spacing required some trial and error.

Another challenge was improving accessibility. Adding ARIA attributes, focus styles, and a skip link involved a lot of research to ensure everything worked correctly for keyboard users and screen readers.


How I Overcame Them

To address the responsiveness issue, I used Flexbox for layout and defined clear min-width and max-width values for the container and card. This allowed the design to adapt while maintaining its structure.

For accessibility, I referred to resources like MDN Web Docs and accessibility guidelines to understand best practices. Testing the solution with keyboard navigation helped identify areas for improvement, such as adding more prominent focus-visible styles and refining ARIA labels for better context.

What specific areas of your project would you like help with? What Specific Areas of My Project Would I Like Help With?

I would love to get suggestions on:

1️⃣ CSS Grid or CSS Libraries

  • How could I recreate the same layout using CSS Grid instead of Flexbox?
  • Would using a CSS library like Bootstrap or Tailwind improve the scalability and maintainability of the project? If so, how should I approach it?

2️⃣ Animations to Enhance Visual Appeal

  • What types of animations could I add to make the project stand out without overwhelming the user?
  • I’m considering animations for hover effects, transitions between elements, or maybe even subtle entrance animations—any ideas or best practices here would be greatly appreciated!

Thank you in advance for your insights! 😊

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on Dias's solution.

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.