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

Blog preview card using Flexbox

accessibility, bem
Michael Okorie•150
@Michael-Okorie
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 I kept the design clean and simple, focusing on making the layout responsive using Flexbox. The challenge was straightforward, but I made sure that the card was fully responsive across all screen sizes.

Next time, I would implement hover effects or animations to make the card more interactive. I’d also consider improving the accessibility of the page by adding ARIA roles and attributes to enhance screen reader compatibility.

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

The biggest challenge was making sure the layout adapted well on mobile screens. Since I was using Flexbox for the layout, I had to fine-tune the card's responsiveness to make sure the card and text stayed properly aligned.

I overcame this by utilizing CSS media queries and adjusting the width and layout properties to ensure a smooth, responsive design on all devices.

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

I would like feedback on the overall structure of the HTML and whether I could improve the semantic elements used. Any suggestions on optimizing the CSS or making the code cleaner would be much appreciated as well. Also, if anyone has tips on adding subtle animations to make the card more engaging, I’d love to hear those.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on Michael Okorie'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.