Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 24 days ago

Responsive Space Tourism Site with Remix and Tailwind CSS

react, remix, tailwind-css, typescript
John Pugh•370
@JohnPugh688
A solution to the Space tourism multi-page website 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?

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!

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 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
Frontend Mentor logo

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 1st-party linked stylesheets, and styles within <style> tags.

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.