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

Space Tourism Multipage Website with NextJS, Tailwind CSS and ShadCN

next, tailwind-css
David Agbaniyaka•200
@agbaniongithub
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?

Key Learnings:

  • Detailed Multipage Website Construction: Through this project, I've reinforced my understanding of constructing intricate multipage websites, showcasing intricate layouts tailored to different devices.
  • Next.js Setup Mastery: I've solidified my ability to set up Next.js projects efficiently. This includes importing multiple fonts from Google Fonts and seamlessly integrating them into my Tailwind CSS configuration file.
  • Tailwind CSS Customization: I've expanded my knowledge on Tailwind CSS by learning how to import various files, such as background images, and incorporating them into my project. Additionally, I've delved into fully customizing Shadow UI components, enhancing the visual appeal and functionality of the project.

Impact: This project has significantly bolstered my confidence in translating designs into fully functional websites and applications. The hands-on experience gained throughout this endeavor has been invaluable, equipping me with the skills necessary to tackle future challenges in web development.

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on David Agbaniyaka'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 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.