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

Reactjs react-router and Tailwind

react-router, tailwind-css, react
Victor•730
@therealmaduanusi
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?

As someone who can get tired of css I was happen that it went well though I expected some confusion but thing later cleared out.

Next time I really need to get prepared if am planning on such kind of project that need such styling by writing things down or making a wireframe of the such box-model

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

My Navigation components always seem to not follow what I want on postion(css property) It was out of the Home, Crew, Destination, Technology components so basically the background-image property doesn't seem to work. So I used position great it worked! but guess what only for(Tablet and Desktop) it couldn't allow me to handle the hamburger-menu then I said ok why don't I remove the postion property on small screen so the hamburger-menu can flow but when I did that the header which was what is handling the postion property flow outside the background-img. Then I said why not put the Navigation component on each component (Home, Crew, Destination, Technology) container from where the background-img is applied and set a min-width media query from 768px postion fixed that way the navigation component doesn't flow outside each component and it worked!!!😁 Now my hamburger-menu can flow relative to the #root element and not the header.

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

Suggestion on css styling would be really great on how you handle yours with ease and not much stress

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 Victor'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.