Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 11 months ago

Space Tourism Website using React,TailwindCSS and Vite bundler

react, react-router, tailwind-css, vite, accessibility
Matthew Kuria•170
@matthewkuria
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 have learnt how to effectively use React Router to navigate through the website pages(routes).I have also learnt how to use and customize react tabs while using data.json file to populate the website from the destination,crew and technology data objects.

What challenges did you encounter, and how did you overcome them?

I have had a challenge applying different background images depending on the route selected.I will be doing more research on how to improve the website.

What specific areas of your project would you like help with?

I will appreciate some help on displaying different background images for different routes as it is in the challenge design.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Edwin Cheng•360
    @edwinc73
    Posted 11 months ago

    pretty cool!!!

    To change the bg just used scss and depending on the section id I changed the image url. I found this to be the best way. you can check out mine to help you get a better idea

    https://github.com/edwinc73/frontend-mentor-advanced-css/tree/master/05-space-tourism https://space-tourism-spa.vercel.app/

    You can also have the image with a repeat none and change the object fit of the image so it doesnt tile.

    you could use max-w-7xl mx-auto which will define the max width to 1280px and then center the containers. This is good so it limits how far apart elements are in a screen.

    i think in some elements there are some strange border radius values I think this is because of border-radius: 50%, the 50% will make it so a rectangle will become an oval shape.

    Marked as helpful
  • Edwin Cheng•360
    @edwinc73
    Posted 11 months ago

    pretty cool!!!

    To change the bg just used scss and depending on the section id I changed the image url. I found this to be the best way. you can check out mine to help you get a better idea

    https://github.com/edwinc73/frontend-mentor-advanced-css/tree/master/05-space-tourism https://space-tourism-spa.vercel.app/

    You can also have the image with a repeat none and change the object fit of the image so it doesnt tile.

    you could use max-w-7xl mx-auto which will define the max width to 1280px and then center the containers. This is good so it limits how far apart elements are in a screen.

    i think in some elements there are some strange border radius values I think this is because of border-radius: 50%, the 50% will make it so a rectangle will become an oval shape.

    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

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

Oops! 😬

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

Log in with GitHub