Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted over 3 years ago

Space Tourism Website using HTML, CSS and Javascript

JP3ra•90
@JP3ra
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


Any queries or suggestions are welcome

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Mojtaba Mosavi•3,760
    @MojtabaMosavi
    Posted over 3 years ago

    1- Spend some time reading about mobile first workflow which is a great way to approach responsive design in my opinion. It also reduces the amout of styles you need to write for a fully responsive solution.

    2- A page like this and many other pages fit perfectly to this structure of new html 5 landmark elements, consider using them more frequently:

    <body>
        <header> </header>
        <main> </main>
       <footer> </footer>
    </body>
    

    3- There are a alot of subtle issues when to semantic markup, for instance <p> elements being used for header. Writing fully accessible markup is not easy but in most cases similar to this answering a simple question like what is this piece of content ? would help a great deal.

    4-I suggest doing you next more project spend a fair amout of time testing what you are developing, for us frontend dev chroms dev tool is of great help.

    Keep coding :=)

    Marked as helpful
  • Ben•300
    @vBenTec
    Posted over 3 years ago

    Hello, What I would suggest is to implement the hover effect on the landing page on the explore button. Another thing you could do is to use the view heights unit on the pages, there is a good use-case for that so you do not have the scroll down the page and all content is within the viewport.

    You could also work a bit more on the responsiveness part. I noticed by resizing your window the page is stuck on the left side and you did not implement the mobile version, so work on your media queries. You could also have a look over your spacing.

    Rest well-done congrats.

    Marked as helpful
  • Aakash Verma•9,500
    @skyv26
    Posted over 3 years ago

    Hi! Honestly telling you, your design is not responsive, because your design not responsive it impact bad user experience that I felt after opening your site.

    So first make it responsive then I will tell next

    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

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

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