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

Responsive space multipage web, using vite +react +tailwind +carousel

react, tailwind-css, vite
Raza Abbas•770
@RazaAbbas62
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


Suggestions and feedback are welcome.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Petrit Nuredini•2,860
    @petritnuredini
    Posted over 1 year ago

    Congratulations on completing your space travel website project! It's fantastic to see how much you've accomplished. Here are a few tips to make your project even better:

    1. Optimize Image Loading:

      • Consider using modern image formats like WebP for better performance and lower bandwidth usage. Additionally, implement lazy loading for images to improve the site's loading time, especially if there are many large images. Check out this guide for more information on image optimization.
    2. Improve Accessibility:

      • Ensure that all your interactive elements, like buttons and links, have appropriate ARIA attributes for better accessibility. This includes adding role="button" to elements that are styled as buttons but not using the <button> tag. Learn more about accessibility in React here.
    3. State Management in Technology Component:

      • In your Technology component, you're mapping over technology twice which might be inefficient. Consider rendering the active technology's details directly without the need to map over the entire array again. You can achieve this by storing the active technology's index in the state instead of the entire object. This way, you can easily access the active technology's details from the technology array using the index. Learn more about React state management here.

    Keep up the excellent work! Remember, each project is a stepping stone towards becoming a more skilled developer. Continue experimenting, learning, and don't hesitate to try new approaches in your future projects. Your progress is remarkable, and I'm excited to see what you'll create next! 🌟🚀

    Marked as helpful
  • Theunis•210
    @theYuun
    Posted over 1 year ago

    Your top menu links appear to be missing their fonts and bold text on the numbers.

    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

Oops! 😬

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

Log in with GitHub