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

3-column preview card component

Sudharshan Murugan•50
@SudharMurugan
A solution to the 3-column preview card component 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 proud of completing the project and successfully creating a visually appealing design using HTML and CSS. This project helped me understand and practice grid layouts, media queries, and responsive design principles. I’m particularly happy with how the color schemes and button hover effects turned out, adding a clean and modern look to the design.

What I would do differently next time: Next time, I would focus on improving my CSS organization by using variables for colors and spacing to make the code more maintainable and scalable. Additionally, I would explore using CSS Flexbox in combination with Grid to achieve a more dynamic and flexible layout. I’d also like to implement accessibility features, such as proper ARIA roles and keyboard navigation support, to ensure the design is inclusive for all users.

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

Challenges I encountered: One major challenge was achieving a consistent layout across different screen sizes while eliminating unwanted spacing between grid items. It took some trial and error with the grid-template-columns property and fine-tuning the gap and padding values to achieve the desired alignment.

Another challenge was ensuring that the design remained responsive and visually balanced on smaller screens. Adapting the typography, button sizes, and padding dynamically for different breakpoints required careful adjustments and testing.

How I overcame them: I overcame these challenges by leveraging media queries and experimenting with various grid configurations. Setting specific breakpoints helped me create a layout that adjusted seamlessly for mobile, tablet, and desktop screens. I also referred to online resources and CSS documentation to better understand responsive design techniques. Finally, testing the layout on multiple devices and browsers ensured consistency and usability.

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

Areas I'd like help with:

Improving Responsiveness: While the layout adapts to different screen sizes, I’d appreciate feedback on optimizing the CSS for smaller screens (below 375px). Are there better ways to manage spacing and scaling without compromising readability or design?

Grid Optimization: Currently, the grid system works, but I’d like suggestions on improving or simplifying the implementation. Are there alternative techniques to manage alignment and spacing more effectively?

Code Structure: Are there any redundant or inefficient parts in my CSS that could be refactored for better performance and maintainability?

Design Enhancements: Do you have suggestions for improving the visual appeal, such as better color combinations, typography adjustments, or button styles?

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 Sudharshan Murugan'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

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.