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

Responsive Space Tourism Multipage Apps using HTML, CSS, and JavaSc

pure-css, jquery
Prayugo Dwi Setiyoko•60
@Prayugo24
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?

What are you most proud of? I am most proud of how I managed to implement the responsive design effectively, ensuring the website looks great across all device sizes. Additionally, I successfully utilized modern web technologies such as CSS Grid and Flexbox to create clean and maintainable layouts. I'm also proud of my attention to detail in replicating the design accurately and incorporating smooth transitions and animations to enhance user experience.

What would you do differently next time? Next time, I would focus more on optimizing the performance of the website by minimizing the use of large assets and utilizing lazy loading for images and resources. I would also aim to write cleaner and more reusable code by adopting a component-based approach using frameworks like React or Vue.js. Lastly, I would allocate more time to testing for accessibility and cross-browser compatibility to ensure the website is inclusive and functions perfectly for all users.

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

What challenges did you encounter? One of the main challenges I encountered was ensuring the layout remained consistent and responsive across different screen sizes, particularly with the intricate design elements like the navigation bar and background images. Another challenge was working with dynamic content and maintaining the site's accessibility standards, such as ensuring proper keyboard navigation and screen reader compatibility.

How did you overcome them? To overcome the responsiveness challenge, I relied on a mobile-first approach and utilized CSS tools like Flexbox and Grid effectively. I tested the design across various devices and screen sizes using browser developer tools to catch and fix layout issues early. For accessibility, I researched best practices, used semantic HTML, and tested the site with tools like Lighthouse to ensure it met accessibility guidelines. When I faced coding challenges, I referred to documentation and sought solutions through the Frontend Mentor community and forums.

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

What specific areas of your project would you like help with? I would appreciate help with the following areas:

Accessibility: While I implemented basic accessibility features, I’d like feedback on how I can improve the site's usability for screen readers and ensure it meets WCAG standards.

Performance Optimization: I'm interested in advice on how to further optimize my website, particularly regarding image loading, asset management, and reducing render-blocking resources.

Code Review: It would be helpful to get insights on how to write more efficient and maintainable code, especially in terms of organizing CSS and JavaScript to keep the project scalable.

Animations and Transitions: I’d love to hear suggestions on how to make the animations smoother and more engaging while ensuring they don’t negatively impact performance.

Cross-Browser Testing: I tested the site on major browsers, but I’d like help identifying and resolving any potential issues in less common or older browsers.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    Trần Thành Danh•1,500
    @TranDanh1122
    Posted 6 months ago

    that good, i learn a lot from it, maybe i can re work my solution with react

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