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

space-tourism

Marcus Silva•260
@silvamaarcus
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


Frontend Mentor Challenge: Space Tourism

Welcome to the Frontend Mentor "Space Tourism" challenge! This is an exciting project that allows you to showcase your frontend development skills by creating a website for a space travel agency featuring various thrilling destinations.

Project Overview

The goal of this project is to build a responsive and interactive website that showcases different destinations for space travel. The site should provide detailed information about each destination, along with crew details and types of transportation.

Technologies Used

The project utilizes the following technologies:

  • HTML5: Content structuring.
  • CSS3: Layout styling, with the use of the SASS preprocessor for more efficient organization.
  • JavaScript: Adding interactivity to the page for a dynamic experience.
  • SASS: CSS preprocessor for better code organization, modularity, and maintenance.

Funcionalidades

  1. Intuitive Navigation: The site offers easy and intuitive navigation to explore the different space destinations.

  2. Destination Details: Each destination has a detailed page with information about the location, crew, and technology.

  3. Responsiveness: The site is fully responsive to ensure a consistent experience across different devices and screen sizes.

Thanks

I would like to express my gratitude to Frontend Mentor for providing this exciting challenge that allows for practical improvement of frontend development skills.

Have fun building! 🚀

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 Marcus Silva'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.