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

Space Tourism Website using Sass, Tailwind and Astro

accessibility, astro, sass/scss, tailwind-css
P
Kamran Kiani•2,780
@kaamiik
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?

This challenge was one of the most difficult I’ve faced so far. The project involved multiple pages, each containing unique information. I put in my best effort to build the site using tools like Tailwind CSS, Sass, and Astro. I should also mention that I followed Kevin Powell’s course on Scrimba during this challenge, which taught me many valuable tips and techniques.

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

Navigation in the header is always a challenge. The styles needed to adapt for mobile, tablet, and desktop views, which added complexity to the code. Additionally, some functionality had to be handled with JavaScript, and Accessibility considerations were crucial.

Apart from the homepage, all other pages featured a tab system to dynamically update the information based on user interaction, whether by mouse click or keyboard arrow navigation. Implementing this was challenging in CSS, JavaScript and Accessibility.

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

I’d love to learn about alternative approaches to building this website. The project includes a data.json file, and I used Astro to develop it. I’m curious if there’s a more efficient way to manage the project with less code. For instance, I currently have four separate pages in the pages folder. Would it be better to use a single page and handle everything dynamically with the data.json file?

I also made an effort to prioritize accessibility in my project, but there’s always room for improvement. If you notice any issues or have suggestions to enhance accessibility, I’d really appreciate your feedback.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Wendy•2,150
    @wendyhamel
    Posted 6 months ago

    Hi! This project takes a lot of time to complete. Nice work finishing it.

    The approach you took with four pages is better than a single page in my opinion. This way you have the right url’s to go with the pages without any workarounds.

    For your accessibility, I read about the tab system and I get your idea there. However, if I try to navigate your site with voiceover, it does not work the way I think it should. I am not able to get it to read the texts aloud. Just the links. Screenreaders use semantic HTML and the DOM order to make Roters. These are helpful for navigating through the content of a site with a screenreader. On your site, the voiceover does not have any rotors available. Apart from the screenreader; When I try to navigate through the site using the tab key, it steps to the texts, which are not parts of your site you can interact with. Navigating through a site with the tab key should only tab between elements a user can interact with, such as links and buttons.

    I am also exploring the improvements for accessibility, so I hope this helps us both in our research to improve.

    Happy Coding!

    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 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.

Oops! 😬

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

Log in with GitHub