
Solution retrospective
I'm proud of how I applied semantic HTML throughout this project, along with using margins and padding thoughtfully to create clean, well-structured spacing between elements.
Next time, I'd focus more on responsiveness from the start, thinking through how the layout should adapt across screen sizes earlier in the process, rather than fixing it after the fact.
What challenges did you encounter, and how did you overcome them?The main challenge I faced was getting the layout to respond well across different screen sizes. Initially, the content wasn't shrinking properly on smaller screens.
I resolved this by setting both width and max-width on the <main> container and on the image element. This allowed the layout to shrink fluidly on smaller screens while still capping how wide it could grow on larger ones.
What specific areas of your project would you like help with?I'd appreciate feedback on my responsiveness approach. I used width/max-width on the container and image, but I'm not sure if there's a cleaner way to handle this.
Please log in to post a comment
Log in with GitHubCommunity feedback
No feedback yet. Be the first to give feedback on Adewusi Abdurrahman’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