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

Space Tourism Website – Tailwind CSS & JavaScript Fetch API

fetch, tailwind-css
Partha Dey•40
@ParthaDey5
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?

I’m most proud of successfully implementing Tailwind CSS for styling and ensuring the website is fully responsive across different screen sizes. Additionally, integrating the JavaScript Fetch API to load dynamic data from data.json was a great learning experience. Debugging deployment issues on GitHub Pages and getting everything live felt like a huge milestone! Next time, I’d focus on structuring my project files more effectively from the beginning to avoid extra adjustments when deploying. I’d also explore animations and accessibility improvements to enhance user experience

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

One major challenge was configuring GitHub Pages correctly. Initially, my project structure caused issues with loading pages, and some assets weren’t displaying due to incorrect file paths. Debugging deployment issues helped me understand how GitHub serves files and the importance of structuring directories properly. I carefully reviewed my file paths and adjusted them to match GitHub’s directory expectations. I also learned how to efficiently update all paths using VS Code’s Find & Replace feature, saving time and effort. Through trial and error, I successfully deployed the project while improving my workflow for future projects.

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

I’d love feedback on my use of Tailwind CSS for styling. Did I structure my utility classes efficiently, or are there areas where I could improve maintainability? Also, I used the JavaScript Fetch API to retrieve data from data.json. I’d appreciate suggestions on optimizing data handling—does my approach align with best practices? Lastly, any insights on improving responsiveness across different screen sizes would be super helpful!

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 Partha Dey'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.