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

Space tourism website using Angular

angular, animation, sass/scss
Tee•240
@thulanigamtee
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


This is the second challenge where I've implemented Angular, and unlike the last challenge, this one was big.

This challenge helped me to get a handle on a lot of staff in Angular. Unlike other frameworks, it has a steep learning curve, but I have so far enjoyed using it. The best way to learn new technology is indeed jumping into building staff with it.

The biggest challenge that I came across when completing this challenge was getting everything to be as close to the design as possible. The overall styling was also a lot of work, and I hope to pick up a different styling approach, such as Tailwind, seeing as it's very popular. Using Angular I added router animations, which is something I found very interesting to do. The background image implementation seemed to be a tricky one seeing as it's a different one for each page, but using Angular to keep track of the route and apply a class to the body seemed to be the best approach rather than adding the images manually on every page.

There are a lot of improvements that can be done, like the images seem to be very slow, so when switching routes/tab there tend to be a delay before they change. There's also some other things I wanted to implement but couldn't because of my limited knowledge with Angular.

Nevertheless, this was a fun one and it came out better than I had anticipated. Feel free to check it out and leave your thoughts.

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