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

Responsive Website using html, css and javascript and bootstrap

animation, bootstrap
Ayoola Victor•190
@lowlifehighway
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?

1.I was able to complete this project using different tools like:html, css, javascript and bootstrap 2.I used different tools for different pages to practice building sites in different ways 3.Added animations to some parts of the project 4.Added a custom loader to all pages but the home page to ensure the page loads after all other components are loaded on

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

1 .Had Issues with using github when I first started but I was anle to get through it with a few tutorials 2 .faced an issue with components on the webpage not loading, was able to overcome it by adding the load event listener to the window 3 . Had an issue with the data imported from the JSON file not loading on some devices and after a tutorial and asking a question on stack overflow figured it out by changing the code for pulling the data from the JSON file from import info from '../data.json' with {type: 'json'}; to try { const response = await fetch('../data.json'); if (!response.ok) { throw new Error(`HTTP error! status: ${response.status}`); } const info = await response.json(); destinations = info.destinations; } catch (error) { console.error('Error loading data:', error); document.body.innerHTML = 'Failed to load destination data. Please try again later.'; return; }

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

I had a problem specifically on IOS devices, when the navigation menu is opened you shouldn't be able to scroll until the menu is closed but for some reason couldn't seem to get it to work on iPhones

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on Ayoola Victor'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.