Four Card Feature Section - Responsive Page

Solution retrospective
Detail containers & components breakdown at the initial stage helps me create a smoother workflow, and it minimises my debugging time. In addition to that, having descriptive class names improves readability, speeds up navigation, and makes CSS easier to maintain. I will keep those 2 in my workflow. That aside, I will use more semantic HTML to reduce <div> usage next time. Also, simplifying my breakpoint strategy to make things cleaner and easier to maintain.
What challenges did you encounter, and how did you overcome them?I still found myself hardcoding certain key properties in CSS to fit a certain screen size, which made the transition less seamless. So, I tested out different units for key properties to achieve a responsive layout. Another issue I had was having too many overrides when it comes to media breakpoints, so I reviewed and cleaned the code to simplify them.
What specific areas of your project would you like help with?It'd be great to hear some tips on achieving a responsive layout in CSS 🙌
Please log in to post a comment
Log in with GitHubCommunity feedback
No feedback yet. Be the first to give feedback on Vell'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