Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 20 days ago

Space tourism multi-page website (astro + tailwind-css)

astro, tailwind-css
P
BarrieDirk•650
@barriedirk
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 is my first time working with Astro in "serious mode", and it's ok. It's easy to understand.

Next time, I will improve the structure of the project.

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

When I executed the script to build the project, some CSSs, like "backdrop-filter," were removed, which was a headache and unexpected.

For now, I have moved the CSS file into a public folder ( astro project ) while I review for a solution in the future.

Another issue I have is the links. Because I am using GitHub pages, I needed to update the href manually.

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

Any suggestions will be welcome

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • legaz•460
    @Legaz-le
    Posted 19 days ago

    Great job you need to make your navbar bigger add padding to it and with background opacity-around 60%.There issue it's might be only with me but when is page in tablet size and you click different page your screen focus on left side of page.

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