Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted about 2 years ago

New version of space-tourism-website using React & React Router V6

react, react-router, tailwind-css
Mr. Ackerman•490
@SFCC5555
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


This is a reimagining of the 'Space Tourism Website' project that utilizes more advanced technologies such as React, React Router v6, and Tailwind. In addition to the previously used technologies like HTML, CSS, JavaScript, and JSON. These enhancements have significantly simplified the development process, transforming the page into a Single Page Application (SPA) with customized routes and subroutes for each section. This allows for an enhanced experience with reduced loading times. While maintaining its responsive design, the new version draws inspiration from the movie 'Interstellar' to provide a distinctive touch.

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

  • Vlad•240
    @vladmee
    Posted almost 2 years ago

    Wow, you came up with your own version inspired by Interstellar! That definitely caught my eye

    I like the way you are handling React. Your project has a good structure. You are making good use of NavLink to navigate between routes. And you manage to put together everything with very little CSS (really, I'm impressed!) All thanks to Tailwind, of course, which you seem to have good knowledge of. Well done!

    The only feedback I have for you is regarding the responsiveness of your pages. While it's following the design on desktop and mobile, you skipped one step: tablet view :)

    This can be quickly fixed with media queries but I want to give you a bigger challenge. Lately I'm reading about the "Fluid design" where, instead of targeting specific resolutions and not caring about anything in between, in this new approach you structure ALL your CSS with dynamic units so it adapts to ANY type of screen.

    This can be achieved using only dynamic units (rem, vw, vh, %) and, the thing that actually changed my perspective a lot: clamp() where you can set a min and max value along with a recommended dynamic value so you have adaptive sizing from mobile (min) to desktop (max) and everything in between (recommended). Here's an example:

    Instead of:

    .technology .navLink {
    width: 40px;
    height: 40px;
    }
    @media screen and (min-width: 640px) {
    .technology .navLink {
    width: 60px;
    height: 60px;
    }
    }
    

    You can use clamp() and ditch the media queries:

    .technology .navLink {
    width: clamp(40px, 5vw, 60px);
    height: clamp(40px, 5vw, 60px);
    }
    

    Hope my feedback helps! As a I already mentioned your solution is already great, it's just the small details to make it perfect for any type of screen. Keep it up!

    Marked as helpful

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 all CSS, SCSS and Less files in your repository.

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.

How does the JavaScript validation report work?

When a solution is submitted, we use eslint to run an automated check on the JavaScript code.

The report picks out common JavaScript issues such as not using semicolons and using var instead of let or const, among others.

The report will audit all JS and JSX files in your repository. We currently do not support Typescript or other frontend frameworks.

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub