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

Learning Card Component with Responsive Design

Emmanuel•60
@Emmxzy
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 the card design came together with clean, responsive styling. The combination of box-shadow and border-radius gave the card a polished look, and the flexbox layout ensured everything aligned seamlessly across different screen sizes. I’m especially happy with how the design captures a professional aesthetic while being minimal and user-friendly.

What I’d Do Differently Next Time Next time, I’d focus more on accessibility features, such as ensuring better contrast ratios and adding ARIA labels for screen readers. I’d also experiment with adding subtle animations using CSS transitions or keyframes to create a more engaging user experience. Lastly, I’d structure the CSS to use reusable utility classes or a preprocessor like SASS for improved maintainability as the project grows.

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

Challenges I Encountered Maintaining Consistent Alignment: Ensuring that all elements (like the tag, title, description, and footer) were perfectly aligned and spaced consistently across different screen sizes was tricky. Small changes in padding or margin often disrupted the design.

How I Overcame It: I used a flexbox layout with clear spacing and alignment rules, ensuring consistent structure. I also relied on browser developer tools to visually debug and tweak spacing.

Responsive Design: Making the card look good on both mobile and desktop required careful scaling of font sizes, paddings, and margins. At first, the layout either looked too cramped on smaller screens or had too much empty space on larger screens.

How I Overcame It: I adopted a mobile-first workflow and used media queries to adjust the card dimensions and text sizes for larger screens. Testing across various devices and screen resolutions helped refine the responsiveness.

Balancing Aesthetic and Simplicity: Deciding how much styling to add while keeping the card minimal yet visually appealing was a challenge. Adding too many design elements risked cluttering the layout.

How I Overcame It: I stuck to a clean and modern design by limiting the color palette, using subtle shadows, and emphasizing typography hierarchy. I also reviewed similar designs for inspiration to ensure a balanced look.

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

Areas I’d Like Help With Accessibility Improvements: While the card is visually appealing, I’d appreciate guidance on enhancing accessibility, such as adding ARIA roles or improving contrast ratios. I’d like feedback on whether the card is fully inclusive for users with visual impairments or those using screen readers.

Optimization for Performance: I want to ensure that my CSS and HTML are as efficient as possible. Suggestions on reducing redundant styles or optimizing for faster load times would be incredibly helpful.

Advanced Design Enhancements: I’d love to learn how to incorporate subtle animations or hover effects to make the card more interactive without overwhelming the user experience. Any advice on modern design trends or tools would be welcome!

Code Organization: Feedback on how I’ve structured my CSS and HTML would be helpful, especially for scalability. Could I organize my code better for future modifications or team collaborations?

Cross-Browser Compatibility: I tested the card in a few browsers, but I’d like to know if there are any edge cases I’ve missed. Suggestions for ensuring the design works flawlessly across all major browsers would be appreciated.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Account deletedPosted 7 months ago

    nice brother

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