Responsive Space Tourism Site with Remix and Tailwind CSS

Solution retrospective
I'm really happy with how the responsive design turned out - everything adapts smoothly from mobile to desktop. I spent a lot of time getting the navigation elements just right for each page and making sure the images look good at all screen sizes. The semantic HTML structure makes it all accessible too, which was important to me. What I would do differently next time: Next time I'd definitely add some testing from the beginning. I'd also play around with more animations for page transitions to make it feel more polished. Maybe try out a different way to manage the content instead of the static JSON data I used. Overall though, I learned a ton building this with Remix and Tailwind!
What challenges did you encounter, and how did you overcome them?The biggest challenge was getting the tab-based navigation to update content without redirecting to a new page. I solved this using React state and Remix's client-side rendering capabilities. I also struggled initially with the responsive layouts for the technology page, but overcame this by implementing a flexible design system with Tailwind breakpoints. Performance was another hurdle - Remix's data loading patterns helped tremendously with this, allowing me to optimize image loading and reduce unnecessary rerenders, resulting in much faster page transitions and a smoother user experience overall.
What specific areas of your project would you like help with?I'd love feedback on my implementation of the image optimization components - particularly how I handled the responsive image loading strategy. Could this be more efficient? Also, I'm curious if my approach to error handling with the custom ErrorBoundary component is following best practices. Finally, I'd appreciate input on my state management for the tabbed interfaces (especially on the destination page) - is there a cleaner way to handle the transitions between content without the setTimeout approach I used? Any suggestions for improving performance further while maintaining the design 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 John Pugh'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