Minimal QR Code Card Layout – Built with Semantic HTML and Responsive

Solution retrospective
I'm most proud of how I was able to build and launch a complete, responsive front-end solution using just HTML, CSS, and a clean, structured layout. It was satisfying to see everything come together in the browser exactly as I had envisioned. I also took time to focus on accessibility and semantic markup, which is something I often overlook but made a point to prioritize this time.
If I were to do it again, I would:
Use a CSS preprocessor like Sass to make the styling more maintainable.
Break the design into reusable components or partials using a templating system like Handlebars or EJS.
Add more browser testing earlier in the process, especially on mobile.
Possibly introduce a build toolchain with npm, PostCSS, or Tailwind if I needed to scale this project further.
What challenges did you encounter, and how did you overcome them?One of the main challenges I encountered was ensuring that the layout remained fully responsive across different screen sizes. Initially, some elements didn’t scale properly on smaller devices, especially images and text blocks. To fix this, I used media queries and experimented with flexbox and CSS grid until the layout adjusted smoothly on all viewports.
Another challenge was maintaining consistent styling without relying on a large framework like Bootstrap. I created a small utility-first CSS structure to keep my styles organized and avoid repetition, which helped streamline development.
I also faced a few moments of uncertainty around accessibility best practices—like how to structure landmarks or use ARIA roles properly. I consulted the WAI-ARIA Authoring Practices and used tools like WAVE and Lighthouse to test and improve accessibility.
What specific areas of your project would you like help with?I’d appreciate feedback or support in the following areas:
CSS organization and scalability – I’d like to learn best practices for structuring CSS in a way that’s easy to maintain as the project grows. Should I consider adopting methodologies like BEM or moving to a utility-first framework like Tailwind CSS?
Accessibility improvements – I’ve made an effort to use semantic HTML and test for accessibility, but I’m sure there are gaps. I'd welcome suggestions on how to make the site more inclusive for all users.
Performance optimization – The site works well, but I’m interested in tips for improving load times, especially for image-heavy pages or slower networks.
Mobile UX – I’d love help identifying any areas where the user experience on mobile could be improved, especially around spacing and touch targets.
Any advice, resources, or examples in these areas would be really helpful!
Please log in to post a comment
Log in with GitHubCommunity feedback
No feedback yet. Be the first to give feedback on wpowell97'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