Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted about 1 year ago

Space Tourism Website using ReactJS and TailwindCSS

react, tailwind-css
Yoga Budiman•300
@ygabdn29
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 challenges did you encounter, and how did you overcome them?

The most challenging things I encounter whilst doing this project is probably how to layout the pages. I think I just try to use what I have learned before to overcome the difficulty on doing the layout and occasionally I need to search for something new and make it work.

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

I'm interested in learning how to create the hover state for the 'Explore' button on the homepage, and I'm also curious about the best approach for handling designs like this, particularly how to manage different breakpoints. I often struggle to keep the design looking good across various common resolutions, especially when the screen is wider than the desktop design or falls between smaller breakpoints. Any advice would be appreciated. Thanks!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Koda👹•3,830
    @kodan96
    Posted about 1 year ago

    hi there!

    I'm doing the challenge rn, I did the :hover with a ::before pseudo element. you set position:absolute; on it, height and width 100%, border-radius 50% and transform:scale(1). in the :hover selector you modify the scaling to `transform:scale(1.5) and boom.

    You can set a transition on it as well if you want.

    For breakpoints there are popular ones: 768px, 1024px, 1440, 1980.. but at the end of the day it depends on your content. if it starts to fall apart around 1200px just place your breakpoint there.

    Hope this helped 🙏

    Good luck and happy coding! 💪

    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 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