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

Space-tourism-website

sass/scss
Jubril Abdulsalam•30
@jubril-a
A solution to the Space tourism multi-page website challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)
Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    Christopher Adolphe•620
    @christopher-adolphe
    Posted about 3 years ago

    Hi @automate-dh,

    Well done for this challenge. I was impressed by the approach you have used to populate the inner pages content. 👍 I have noticed a few things that you might want to check in order to improve your solution.

    • On the home page, instead of using an <h5> and an <h1> for the heading, you could have implemented it this way and apply the property styling to the nested <span> element.
    <h1><span>So, you want to travel to</span>Space</h1>
    
    • The overall markup of the home page could be simplified by removing some of the nested <section> elements like so:
    <section class="main-text-container">
      <div class="col-1">
        <h1 class="uppercase"><span>So, you want to travel to</span>Space</h1>
        <p class="body-text">Let’s face it; if you want to go to space, you might as well genuinely go to outer space and not hover kind of on the edge of it. Well sit back, and relax because we’ll give you a truly out of this world experience!</p>
      </div>
    
      <div class="col-1">
        <a class="btn-explore" href="space-tourism-website/destination.html">explore</a>
      </div>
    </section>
    

    In doing so, you can then apply the styling of the button directly to the <a class="btn-explore"> and achieve the hover effect by using pseudo elements.

    • It would be more appropriate to use an <h1> element for the heading of the inner pages instead of an <h5>, like:
    <h1><span>01</span> Pick your destination</h1>
    
    • As a general observation for the inner pages, I think there is an over usage of the <section> element. By definition, it is used for thematic grouping of content with a heading which is not always the case for those inner page. You could simplify the markup pretty much like suggested for the home page.
    • In your Sass files, I would suggest to refrain from using id as selectors as this hinders reusability and also try to keep the level of nesting to a maximum of 3 levels to avoid overly specific selectors.

    I hope this helps.

    Keep it up.

    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
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 1st-party linked stylesheets, and styles within <style> tags.

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.

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub