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

Multi-page Space Tourism Website using HTML, CSS and JavaScript

Jaime Contemprato•90
@Jaime-Cont
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?

What I'm most proud of is taking on a difficult challenge, I felt like I needed to take on easier challenges but I was looking at this challenge and was thinking of the ways I could accomplish it, and here I am with it accomplished! I'm proud that I learned from my previous challenge and incorporated them onto this challenge, mainly the mobile-first workflow.

If I were to do anything differently next time it would be better planning of how my files would look like, because I had most of my CSS files into one CSS file previously which created complications, and it also made it complicated when I made a folder and put all my CSS files there, but once I organized all of it it helped my workflow for the better! Will be more organized for cleaner coding!

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

The challenges I encountered include:

  • Not knowing how to retrieve and use data from JSON files.
  • Trouble with CSS Flexbox, I would run into situations where it would look like how I wanted it, but had to trial and error some stuff in order to make it responsive, cause it would look good on a maximized browsers but when I would test the responsiveness, texts would be on top of each other.

I overcame them by:

  • Researching on how others use data from JSON files and learning what I can do with it for the project at hand.
  • By trial and error and research on CSS Flexbox, I was patient with learning how to deal with the situation and was happy to get a result that looked amazing.
What specific areas of your project would you like help with?

The areas in my project I would like help with would probably be the following:

  • How to better use Grids and Flexbox, because there were times that it would look good on a maximized browsers but when I would test the responsiveness, texts would be on top of each other.
  • JavaScript APIs and possibly Frameworks, because I originally intended to learn React for this project to broaden my knowledge and experience, but I was harder than I thought.
  • Better CSS, maybe learning Tailwind CSS? I feel like I did a good job with the CSS with this but I feel like I could do more, especially more that would be good for an industry standard.
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 Jaime Contemprato'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.