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

Space tourism multipage website

Bárbara Damasceno•320
@barbaradamasdev
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


I did transition on cards to be more interactive. I loved to do this challenge. Really excited about the result.

Any feedback will be amazing!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Vlad•240
    @vladmee
    Posted almost 2 years ago

    Great job! Your project looks excellent, almost pixel-perfect!

    I like that you added extra stuff, I noticed the flip animation on the mobile menu toggle. That's a nice touch!

    The animation on the tabs is nice too but, as @Cor-Ina already mentioned, this is not really a UX improvement. Yes, users prefer reduced motion, but another thing you should consider here is to not move the controls. The tab buttons should always be predictable for the user. Imagine someone wanting to check all options before making a decision. They would want to click on each tab in a sequence. In your solution, their tab buttons run away before they can click. They are coming back but the brain tells you something else until the animation is done. You know what I mean, right?

    In this case, I would consider other types of animations and only affecting the content (image, text etc.) elements that change! You can have the text blink (opacity animation) or reveal top to bottom (size animation). That's actually a UX improvement because the user will be aware that those elements updated and she needs to read it again. Hope that makes sense! Let me suggest animista which is a nice collection of CSS animations.

    And, if you want to bring it to another level you could even have the elements revealed in a sequence, one by one. That would be a great practice for you if you haven't played with delay and triggers before!

    Other than that you nailed it. It looks exactly like the designs! Maybe revise your CSS a bit. I've seen a few things like max-width: 110vw; This translates to: this element's width can't be more than 110% of the viewport width which is... impossible unless you have horizontal scroll (not advised!) So I think this line doesn't have any effect.

    Keep up the good work! Looking forward to seeing your next projects!

    Marked as helpful
  • Cor-Ina•250
    @CorinaMurg
    Posted about 2 years ago

    Hi Barbara,

    This was not an easy project to complete. Congratulations!

    One suggestion: add a "prefers reduced motion" media query for accessibility reasons.

    The transitions make the site more dynamic, but could be problematic for certain users. People with motion or visual sensitivity may experience discomfort when exposed to animation on the screen. For them, reducing motion can make digital content more accessible and comfortable to consume.

    Beautiful work! Corina

    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

Oops! 😬

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

Log in with GitHub