Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted about 1 year ago

build with vite react js

vite, react
Shay Asanova•50
@shay122990
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?

Really glad that I took on this challenge, and implemented new tools, separated components, learned that you've got to set a _redirect file when publishing to production. I've also tried pagespeed insights to see if my code is semantically correct and has good speed, accessibility and seo ratings.

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

This was a bit challenging to create, especially using vite for the first time and its config with react-router-dom, but eventually i got it working. Most challenging was thinking about the architecture of the project and what I wanted to prioritize. With this project I challenged myself to think ahead. Perhaps in the future i want to add more pages, or add more features, so I started to create separate components, something that would be easily maintainable and understandable in the future. Learning how to create "Tabs" was new to me. I've used it on all three pages,and then realized I could separate that logic. I've used flexbox, and honestly i wish i used grid instead. (something to work on in the future). I started building each route with its respected mark up, most of it is repeatable and some of its css could be moved to a global scope, but perhaps that decision will be made later, as of now i want to keep each css to its component so it would be easier to read and relate later.

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

I had a challenge with setting a background image, and its different changes per screen size, not sure if i've done it right? I've set it to an individual container of each page, then there was a challenge to set the navbar on top and make sure there was no overflow. It works well, but if theres a better way of doing it, please let me know.

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 Shay Asanova'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 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.